Credits
On this page
Hold, capture, release #
Hold when the job starts. POST /articlesanswers withcreditsHeld.Capture when the job finishes. The job.donewebhook carries the credits captured.Release if the job fails or is cancelled. A refundedevent ends the stream andjob.failedcarriesrefunded.
refunded event with reason: "unused" carries the total, just before done, and does not end the stream. The primary article is never held back by a version. See Write in several languages.
What costs credits #
| Action | Credits |
|---|---|
length short or standard) | |
length long) | |
Two rules about scopes #
Caps that stack #
| Layer | What happens |
|---|---|
insufficient_credits. For a key or an agent the message carries no numbers. | |
budget_exhausted, with resetsAt and Retry-After. Days are UTC; the cap resets at 00:00 UTC. | |
plan_limit. |
Credits are never shown to a key or an agent #
POST /briefs/{id}/estimate returns enough: true or false, and a refused start returns a generic 402. The check is whether the trial is still running, the balance covers the cost, and today’s spend plus the cost fits the credential’s cap.