Crédits & facturation

Credits model

• Public API billing is credits-only.
• One returned business resource or collection row costs one credit.
• Every active workspace plan includes 10,000 recurring credits per month.
• Top-up credits carry over and do not expire.

Consumption order

1. Recurring monthly credits are consumed first.
2. Top-up carry-over credits are consumed second.

Metered collection endpoints use reservation and settlement in the backend, so the final cost is based on returned results rather than requested limits alone.

Helpful endpoints and headers

• GET /v1/usage exposes the runtime balance snapshot.
• Successful metered responses can include X-Usage-Cost, X-Credits-Remaining, and X-Credits-Source.
• Shell endpoints like /v1/me, /v1/workspace, /v1/usage, /v1/openapi.json, and /v1/docs remain unmetered.

Top-ups

Manual and automatic top-ups are supported from the webapp billing layer. The fixed exchange rate is $1 = 1,000 credits, with a minimum top-up amount of $10.