Credits and costs
Masko runs on credits, shown in dollars of usage: a picture uses $0.125, a five-second animation of a pose $1.25 and a second of talking $0.25. Bigger purchases give more usage for the money.
What generation costs
| Operation | Cost |
|---|---|
| One image, image edit, or preview | $0.125 per generated image |
| Animation, Standard | $0.25 a second (2 to 15 seconds) |
| Source image for an animation | $0.125 when a new image is needed |
| Talking animation | $0.25 a second ($15.00 a minute), up to 5 minutes, settled once the voice is recorded |
Talking estimate (dry_run: true, or a call above its credit ceiling over MCP) | Free |
| Three voice samples | $0.125 |
| Logo | $0.625 |
| SVG from a logo or image | $3.75 |
| Background | $0.375 |
| Sticker from an image | $0.125 |
| Animated sticker from an animation | Free |
| Cursor follower (nine directions) | $1.13 |
| Reversing an existing video | Free |
| Hosting on assets.masko.ai | Free up to 50,000 views a month, then $0.125 per 1,000 views |
Background removal, format conversion, resizing, uploads, reading metadata, analyzing an image or website and reviewing a generation plan are free. Preview images are paid even though their URLs expire.
New accounts get $3.75 to start. Credits never expire.
What credits cost
A dollar buys a dollar of credits, whatever the amount: $10 gives $10 of credits and $1,000 gives $1,000. There is no bonus for bigger purchases, and credits never expire. Any amount from $10 works in Billing.
| You pay | About this many five-second animations | Or this much talking |
|---|---|---|
| $15 | 12 | 1 minute |
| $50 | 40 | 3 min 20 s |
| $200 | 160 | 13 minutes |
| $1,000 | 800 | 66 minutes |
Check your balance
Run masko credits (or --json), or await Masko.client().credits() in the TypeScript SDK. masko whoami shows the account and workspace it belongs to.
curl https://api.masko.ai/v1/credits \
-H "Authorization: Bearer $MASKO_API_KEY"{
"data": {
"subscription": 450,
"topup": 100,
"total": 550
}
}The API, the SDK and the masko command count in credits, worth $0.125 each: a total of 550 is $68.75. Subscription credits are spent before top-up credits. Buy credits and see terms in Billing. Hosting is free up to 50,000 views a month, then $0.125 per 1,000 views (hosting).
Buy credits from the API
Create a Stripe-hosted checkout page for your credential's workspace; it never charges a saved card or buys automatically. Team purchases require the active team owner.
curl https://api.masko.ai/v1/credit-checkouts \
-H "Authorization: Bearer $MASKO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: credit-purchase-001" \
-d '{"amount_cents":2000}'amount_cents: whole USD cents from 1000 to 1000000 ($10 to $10,000). Send no organization ID, price, credit quantity, payment method or return URL.- The response has
id,url,credits,amount_cents,currency,organization_id,expires_atandstatus_url. Openurlto confirm the final amount on Stripe; never give card details to an agent. - After a timeout, reuse the same
Idempotency-Keyand body (replays last 24 hours). If the URL expired, check status before buying again.
curl https://api.masko.ai/v1/credit-checkouts/CHECKOUT_ID \
-H "Authorization: Bearer $MASKO_API_KEY"Only its creator can read a checkout, from the same workspace. A paid checkout with credits_added: false is still delivering credits, so check again rather than paying twice; balance is the workspace balance, not a receipt. Only Stripe's verified webhook grants credits, once; reading status never does.
The MCP server has no tool that buys credits: agents spend the credits already in the workspace you connected and point you to Billing. Agents that call the REST API can create a checkout link as above, only when the user asks to buy credits.
Approve a plan
For canvas generation, dry-run first, then submit the same selection, approved plan ID and graph hash, so a changed graph cannot silently cost more. Over MCP, estimate_canvas_generation returns a plan_id, which generate_canvas takes with a credit ceiling.
Credits are allocated when work is accepted, and a client timeout does not prove failure. Check the job or run before retrying, and use persisted idempotency keys where supported; /generate has no run-level replay.
Insufficient credits
A rejected request returns HTTP 402:
{
"error": {
"code": "insufficient_credits",
"message": "Insufficient credits",
"details": {
"required": 21,
"balance": 5
}
}
}Rely on error.code; messages and optional details differ by endpoint. Buy more in Billing.
Failures and refunds
A partly failed run can still hold successful paid assets. Runs report allocated_credits, credits_refunded and refund_status where available; a missing refund value promises nothing.
If the source video succeeded but transparent formats failed, use media repair instead of a new paid generation (generation progress and repair). Over MCP, generate_canvas repairs those files for free.
