Credits
How credits are consumed across endpoints.
Credit costs (live endpoints)
| Endpoint | Credits |
|---|---|
GET /v1/health | Free |
GET /v1/templates | Free |
GET /v1/templates/{id} | Free |
GET /v1/templates/{id}/image | Free |
GET /v1/trending | Free |
GET /v1/models | Free |
POST /v1/meme/caption | 1 |
POST /v1/meme/generate | 2 |
POST /v1/meme/ai-image | 3 |
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.
| Endpoint | Credits |
|---|---|
POST /v1/meme/from-image | 2 |
POST /v1/meme/branded | 3 |
POST /v1/meme/gif/generate | 4 |
POST /v1/meme/remix | 5 |
POST /v1/video/generate | 8 |
POST /v1/meme/batch | Sum 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_starttimestamp
Insufficient credits
If a request would push you negative, you'll get a 402 INSUFFICIENT_CREDITS response
before any work is done.