Account & usage

Your account exposes balance, credit grants, charge history, and async job summaries. All of it is read-only from the API; billing settings are managed separately in the Developers Portal.

Three resources cover this:

• GET /api/v1/me — balance, pricing tier, signup trial, and active credit grants.
• GET /api/v1/usage — paginated charge history, one row per billed event.
• GET /api/v1/jobs — paginated list of async jobs (forecasts).

All monetary fields are integer EUR cents (100 = €1.00). Top-ups, payment methods, and auto top-up settings are managed in the Developers Portal — not via this API.

Balance and available balance

Your account has two balance figures. The ledger total (balance_eur_cents) reflects all top-ups and charges. The available balance (available_eur_cents) is lower when async forecast jobs are running, because a hold is reserved until each job completes or fails.

Credit grants

Credits are held as individual grants (signup trial, top-up, partner credit, and similar), each having its remaining balance, expiry date, and source. Grants are consumed in expiry order, soonest-to-expire first.

Usage history

Each billed event produces a row in the usage history, whether an async job settling or a call completing. The list is paginated and sortable, suitable for building usage reports or auditing spend.

Job list

Async jobs (forecasts) can be listed with lightweight summaries: status, submission time, and final cost. For a single job's full state and artifacts, use GET /api/v1/forecasts/:id.

Top up balance

Credit top-ups and payment methods are managed in the Developers Portal, there is no API to initiate a top-up or update payment details.

See also

• API reference: GET /api/v1/me · GET /api/v1/usage · GET /api/v1/jobs.
• Clients: Using curl · Python SDK · Go SDK · R SDK · Java SDK.