Build video into your workflow.

Choose the integration for your job. Read setup, access and costs before sending a request.

Two integrations. Different jobs.

AI Studio REST API →Personalize an existing template or campaign from your server. Use a Client ID and Client Secret with Basic Authentication.Hosted MCP →Let Claude Code or Cursor create Speakeasy videos, personalize AI Studio templates or prepare LeadR campaigns. Review costs and approvals for each product. Connect using an MCP bearer key.

Integration qualification in progress

These beta guides distinguish deployed contracts from completed customer tests. End-to-end account, generation and client qualification is pending. Review the status in each guide before launch.

Know the access and cost before starting.

REST credentials: Settings → API Keys → Generate new key. Use the Client ID/Client Secret pair for documented Studio generation routes.
MCP credentials: Settings → API Keys → Generate MCP key. A separate bhm_mcp_ bearer key expires after 90 days; replacement revokes older MCP keys.
Generation costs: Requests use production credits. Review Plan & usage and the exact generation estimate; MCP preparation stops before the paid video render. Paid starts require approval.
Account scope: Use owned assets and account permissions. A key does not grant admin access or bypass product, balance or rollout restrictions.

Everything you need stays public.

REST quickstartA one-recipient request, accepted IDs, status polling and playable output.Claude Code setupHosted HTTP connection with an MCP key.Cursor setupPersonal client configuration and tool discovery.Download Python exampleHidden credential prompts, one submission, local IDs and resumable polling.Public SwaggerDeployed schema. Internal/admin routes are not customer integration capabilities.Get integration helpConfirm restricted account access, production volumes or an uncertain generation outcome.