Skip to main content
The Crevio API is metered pay-per-call: AI work is billed in credits drawn from your account balance. Plain CRUD (listing products, reading orders) is cheap or free; the spend comes from AI operations — chat messages, media generation, Tasks, web research, and phone calls. Two endpoints give you full visibility: GET /usage for your current plan, balance, and spend breakdown, and GET /usage/transactions for the individual metered charges behind it.

Check your balance and spend

GET /usage returns your plan, remaining credit balance, and a per-operation spend breakdown for the current billing period.
A real response:
object
Your current plan: name, status, is_paid, on_trial, trial_ends_at, renews_at.
integer
Credits remaining on the account.
object
Period spend: period_start, period_end, total_credits, and by_operation[] (each { operation, description, credits }).

See individual charges

GET /usage/transactions lists each metered charge so you can attribute spend precisely.
It returns the standard list envelope (object: "list", data, has_more) — paginate it with limit and starting_after like any other list endpoint.

What consumes credits

Operations that run AI or external compute are metered: Reading and managing your own data (products, orders, customers, webhooks) is not AI-metered.

AI media pricing

Media generation is priced in USD per unit and converted to credits. Pick the cheapest model that meets your quality bar — the default is the most economical.

Images (per megapixel, unless noted)

Video (per second, unless noted)

Audio / TTS (per 1,000 characters)

Generated media lands in your Media Library as a file_… id you can reuse — for example in a product’s images array. Always reuse the file id rather than re-generating.
Run GET /images/models, GET /videos/models, and GET /audio/models for the live model list — new models appear there before this table is updated.

Next steps

Conventions

List envelopes and pagination apply to transactions too.

Errors

How balance and rate issues surface.

MCP & agents

Tasks and agent work are the main credit consumers.

API reference

Full usage and media generation schemas.