HeyGen Stripe Projects API key vs how you get a Sume key
HeyGen lets an agent provision a key with stripe projects add heygen/api. Sume keys are created in the dashboard, workspace-scoped and shown once.
HeyGen documents a Stripe Projects flow where an agent runs stripe projects add heygen/api and gets a key funded to a budget you set. Sume has no equivalent flow in its docs: you create the key in the dashboard, it is workspace-scoped, and top-ups are a dashboard operation.
HeyGen steps are from its Stripe Projects page; Sume steps from API keys and Credits, read 2026-10-01.
How does the HeyGen flow work?
The agent finds heygen/api in the Stripe Projects catalog, Stripe passes the user's identity to HeyGen, a Stripe payment token funds the account up to a budget, and the returned key is written to .env. The page says the agent never sees a card number, and warns that provisioning a paid service spends real money against the budget you set.
Non-interactive use needs billing already configured and the flags --json --yes --confirm-paid-service --accept-tos.
How do I get a Sume API key?
Use the API Keys dashboard to create and manage keys for the Developer API. Keys are workspace-scoped, and the dashboard reveals the full secret only when a key is created, so store it in a secret manager right away. Sume API keys, scopes and hosts covers the header and hosts.
How does an agent pay on Sume?
Not through the API. The credits docs say the dashboard can start a Stripe-backed manual top-up when billing is configured, and that API clients should treat top-ups as dashboard operations. The public Developer API exposes balance and usage reads, not a top-up creation endpoint.
What is the practical difference?
A person has to do the key and top-up steps once.
| Step | HeyGen with Stripe Projects | Sume |
|---|---|---|
| Create a key | stripe projects add heygen/api | API Keys dashboard |
| Fund it | Stripe payment token up to a budget | Dashboard top-up |
| Where the key lands | Project .env | You store it; shown once |
| Read balance by API | Not covered on the page | Balance and usage reads |
Sources
Related posts
More in Developers
- HeyGen studio video scene limit: 50 scenes, and Sume's 4-60 s plan
HeyGen studio videos allow 50 scenes and 30 minutes per scene. Sume multi-scene video_inputs share one 4-60 second window and one resolved avatar.
- Luma API 429 requests per minute: sliding window vs Sume
Luma counts requests in a sliding 60-second window and returns 429 if RPM or concurrent jobs fails. Sume returns 429 rate_limited: back off, reuse the key.
- Luma API concurrent jobs limit vs Sume plan concurrency
Luma caps active generations per API client and answers 429 when full. Sume ties concurrency to your plan and queues extra jobs until queue_full.
- Luma API video URL expires after 1 hour: what to do on Sume
Luma Agents API video URLs are presigned and expire after 1 hour. On Sume, a completed job is fetched with your API key from the /content endpoint.
Written by Sume