Where the cost of a call comes from

The costs tab breaks the call down by component: transcription, model, speech, telephony and the rest, each with the provider, the model and the rate basis. Where there is no published price, the row says why instead of showing a silent zero.

Engage → Calls → your call → Costs

The usage page is a filterable table of every metered usage event: component, provider, model, quantity, cost. It exports to CSV, and the export carries the provider cost as well as what you were charged.

Billing → Usage → period filter → Export

Credits move through an append-only ledger. The balance is the sum of the ledger rather than a column somebody rewrites, and a reconcile command proves it. A call starts only if the wallet can plausibly cover sixty seconds of it.

Billing → Credits → Buy credits · Auto-reload

The overview shows spend by component over the last thirty days in three columns: share, provider cost, and what was billed. The difference between the last two is the margin, and you can work it out yourself, line by line.

Billing → Overview → “Spend by component — last 30 days”

• The components of one call add up to what usage shows for the same call.
• The CSV export downloads with a line per usage event.
• The balance on the credits page equals the sum of the ledger entries.

• There is no button in the console to add a card. Payment methods are managed only through the API, and buying credits needs Stripe configured.
• The plans and add-ons page is read-only. There is no upgrade flow in the console.
• Setting the margin is a staff tool, in the internal platform panel, not in your console. What you get is cost transparency: the provider cost sits next to the billed amount on every row.