Usage and metering

Every billable thing connect0 does is measured, priced, and then burned from your credit wallet. This page explains that pipeline — from a single metered action to the number on your dashboard — so the usage view reads like a receipt, not a mystery.

What a usage event is

Each metered action emits one usage event attributed to your account (and, where relevant, a project). An event records a product — the kind of work — plus the quantities that drive its price. The products you'll see include:

• chat, embedding, image_generation, speech_to_text, video_generation, and other model-router modalities — priced on token or per-output unit counts.
• web_fetch, web_search, maps — paid tool calls.
• sandbox_exec — sandbox compute time.
• connector_materialise / connector_refresh — connector work.
• file_upload / file_download — data transfer.
• storage — data you keep, metered per GiB-month.

Model calls carry token counts (token_in, token_out, cached-read tokens) and whether the call used your own key (BYOK). Control-plane reads — listing connectors, viewing dashboards — are not metered.

From events to credits

Usage events don't bill one at a time. Once an hour, a rollup groups your events by account, product, and unit and prices each line. That priced total is then converted to credits (1 credit = $0.01) and burned against your grants, oldest-to-expire first. Because burn is computed after the fact, in-flight work can briefly overshoot before the next rollup catches up.

Rollups are idempotent: re-running an hour replaces that hour's burn rather than double-charging. Model-router calls are priced at the moment of the call (from the model catalog, plus the BYOK orchestration fee), while other products price from the pricebook at rollup time.

Where to read your usage

The canonical view is /a/<slug>/usage. It shows month-to-date spend in credits (with dollar equivalents), a breakdown by product, modality, model, and BYOK vs platform-key, a 30-day activity chart, and recent events. (/a/<slug>/billing/usage redirects here — there's a single usage surface.) Your live balance and grant expiries sit in the wallet at /a/<slug>/billing/credits.

An empty run that cost nothing

If an agent run finished but shows no model call — an empty unit count — no metered model work happened. That's a dispatcher short-circuit (for example a missing platform key or no runtime model), not a metering bug, and it burns no model credits. See Why did my agent run fail? to diagnose it.

Where to go next

• Spend controls — cap spend and set alerts on top of metering.
• Credits and pricing — how the wallet those burns hit actually works.