Billable usage
Completed checkouts only. Attempts are never metered — charging for attempts would mean earning more when the agent fails, which is backwards for a product whose entire problem is reliability.
The default window is the current calendar month (UTC), which is the unit tenants are billed in.
Requires the usage.read scope.
A subject-bound key cannot call this. Billing is between us and the tenant; an end user’s key reading the account’s total spend and order volume would be a leak between your own customers. 403.
Authorizations
Authorization: Bearer ck_test_… or ck_live_…. There is no other auth scheme — no query-string keys, no request signing, no OAuth.
Query Parameters
Inclusive start. Any Date-parseable string. Defaults to the first instant of the current UTC month.
Exclusive end. Defaults to now.
Response
The summary for the window.
The billable number.
Completed checkouts per UTC day, cut at UTC midnight to match from, to and every other timestamp the API returns — the bucket a checkout lands in never depends on the server's timezone or yours. Days with no completions are omitted, not zero-filled.
Gross merchandise volume by currency. Reporting only — billing is per completed checkout, not a percentage.