HeyGen videos:write and videos:read vs Sume scopes mcp:read/write
HeyGen needs videos:write to create and videos:read to poll. Hosted Sume OAuth has mcp:read and mcp:write, no paid scope; spend is wallet admission.
HeyGen's heygen-video-1 creation needs an API key with videos:write, and polling needs videos:read. Sume's hosted MCP OAuth has two scopes: mcp:read (required) and mcp:write (opt-in). There is no mcp:paid scope; paid submits go through wallet admission.
HeyGen facts are from its API changelog; Sume facts from MCP OAuth and MCP tools and gates, read 2026-10-01.
How does HeyGen split create and poll?
Per the changelog, API keys need videos:write to create and videos:read to poll, and you send an idempotency header on submit so a retry does not start a second generation.
How do Sume's scopes compare?
| Session | What it can do |
|---|---|
OAuth mcp:read only | Read-only tools; mutating or paid calls return insufficient_scope |
OAuth mcp:read + mcp:write | Full hosted tool set |
| API key | Full hosted tool set |
Is there a paid scope?
No. The docs say paid submits are wallet and admission, not a scope. Mutating and paid tools are hidden until the session has mcp:write or an API key, and write or paid tools require an idempotency_key. Granting write always includes read.
Which setup fits a polling-only client?
Grant only mcp:read to a client that reads job state, and add mcp:write where something creates jobs. Preview spend with dry_run and cap it with max_spend_usd, which is enforced only when provided. See API keys vs OAuth for MCP.
Sources
Related posts
More in Developers
- HeyGen asset upload max size: 32 MB, and what Sume does instead
HeyGen's POST /v3/assets caps files at 32 MB, URLs included. Sume has no asset step: requests take public HTTPS URLs, and oversized bodies return 413.
- HeyGen Assets folders (flat) vs Sume media inputs by HTTPS URL
HeyGen Assets library folders are app-created, flat, and usable as folder_id destinations. Sume takes media as public HTTPS URLs, with no folder step.
- HeyGen audio file size limit (MP3/WAV 32 MB) vs Sume 10 MB
HeyGen audio_asset_id takes MP3 or WAV up to 32 MB. Sume's Fabric audio_url must be on the Sume media host and at most 10 MB. What each rule means.
- HeyGen audio to video max length: 10 or 30 min vs Sume 300 s
HeyGen's pages say 30 minutes per audio-to-video request and 10 minutes for avatar audio input. Sume's Fabric route caps duration_seconds at 300.
Written by Sume