The API charges nothing of its own: it uses the AI credits of the account the key acts for, exactly like the Memojin app. Only two operations use them; every other one is free.
What uses credits
| Operation | Credits |
|---|---|
POST /v1/contents/{contentId}/memocard-generations | One ai_card unit per memocard generated |
POST /v1/contents/{contentId}/question-generations | One ai_card unit per question generated |
| Every other one (reads, creations, updates, deletions, search) | None |
The estimate before generating
The 202 response gives estimate.units, the number of items the job plans to generate, repeated in the Memojin-Credits-Estimate: ai_card=12 header. The value of a unit is set by Memojin’s credit catalogue; the app shows it as a share of the account’s monthly allowance.
/v1/contents/{contentId}/memocard-generationsScope generations:writecurl -X POST "https://api.memojin.com/v1/contents/3f1c2b0e-8d4a-4f7e-9a51-3c2d1e0f9b87/memocard-generations" \
-H "Authorization: Bearer $MEMOJIN_API_KEY" \
-H "Idempotency-Key: 6f1c2b0e-8d4a-4f7e-9a51-3c2d1e0f9b87"{
"jobId": "9b8a7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
"status": "pending",
"estimate": {
"operation": "ai_card",
"units": 12
}
}When credits are used
- While the job runs, never at request time.
- A refused request (
402 insufficient_credits,422,404…) costs nothing; neither does an idempotent replay. - With a
mj_test_key, nothing is generated nor used (ai_card=0).
Out of credits
When the account has too few credits left, the generation is refused with 402 insufficient_credits and nothing starts. Credits renew with the account’s plan; a higher plan gives more (see pricing).
API access
API access itself is not charged per call: it is opened on request, by our team. Access included in plans Coming soon will be announced in the changelog.