Skip to main content
POST
Track and Consume Credits
Auth: secret key only. The customer, Feature, and optional Credit System must belong to the authenticated organization.
A successful response includes the operation ID, exact credits consumed, remaining total, and source deductions with their balance-source IDs. Insufficient credits return allowed=false without allocations or a Core event. Retry HTTP 503 with the same idempotency key. Reusing a key with a different payload returns 409. For staged validation and canary guidance, see Credit Rollout and Acceptance.