createa.meme

Credits

How credits are consumed across endpoints.

Credit costs (live endpoints)

EndpointCredits
GET /v1/healthFree
GET /v1/templatesFree
GET /v1/templates/{id}Free
GET /v1/templates/{id}/imageFree
GET /v1/trendingFree
GET /v1/modelsFree
POST /v1/meme/caption1
POST /v1/meme/generate2
POST /v1/meme/ai-image3
POST /v1/meme/remix5
POST /v1/animate (beta)10 (480P) · 16 (768P) · 2 for a cache replay
GET /v1/animate/{job_id}Free

Video animation is invite-only beta — the credits above apply once your key has access. Failed animations auto-refund, and repeating a popular template + motion combo replays instantly from cache for 2 credits.

Roadmap pricing (not yet live)

These endpoints currently return 501 NOT_IMPLEMENTED. Pricing below is what they'll cost once they ship — see API Status for release timing.

EndpointCredits
POST /v1/meme/from-image2
POST /v1/meme/branded3
POST /v1/meme/gif/generate4
POST /v1/meme/batchSum of items

Rules

  • Credits are deducted atomically before generation (prevents race-condition abuse from concurrent requests)
  • Failures auto-refund — generation errors return your credits within seconds
  • Test keys (cam_test_*) get a small separate pool (10 credits per key) so you can verify your integration without spending against your live quota. They use the same models and same moderation as live keys.
  • Credits reset monthly based on your period_start timestamp

Insufficient credits

If a request would push you negative, you'll get a 402 INSUFFICIENT_CREDITS response before any work is done.

Rate Limits

Per-key sliding-window limits enforced via Upstash Redis.

Errors

Error codes, HTTP statuses, and how to handle them.

On this page

Credit costs (live endpoints)Roadmap pricing (not yet live)RulesInsufficient credits