For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt, and this page is available as Markdown at /automcp/v1/billing.md.
Delino documentation

Verified external-cost settlement

Availability: The AutoMCP production service is not yet deployed. This page and its examples describe the committed v1 contract for integration planning; requests to the API URL will not succeed until the runtime is released.

Text and memory usage is verified from OpenRouter final usage and generation evidence. Realtime voice uses actual OpenAI usage and the version-pinned price table for the call. Failed or canceled work is chargeable only for verified cost already incurred.

AutoMCP sums exact verified provider cost without binary floating point or intermediate rounding, applies exact cost × 7/4 (cost plus 75%), and rounds once at the end to integer USD millionths. For example, $0.02 becomes a submitted charge of $0.035. Delcore validates and deduplicates the provider evidence and records exactly that submitted debit; it does not recalculate the price. Estimates are never finalized as charges, so missing evidence leaves a Run awaiting evidence/settlement and can block new paid execution for the workspace.

The pre-execution spend check is not a reservation. Concurrent paid Runs can therefore consume the same remaining balance and make the workspace balance negative; customers must not treat the check as a hard per-Run prepaid limit.

Provider evidence and settlement are idempotent. OpenRouter funding fees, infrastructure, customer-paid API charges, application registration, storage, and tool-call counts are excluded. MCP work with no external AI cost settles at zero while authorization and lifecycle controls still apply. While evidence or settlement is pending, AutoMCP intentionally withholds the final Run payload and completion webhook; this is a billing gate, not a delivery failure. Those final outputs are released only after settlement succeeds. Already streamed text/audio cannot be recalled if settlement is delayed.

AutoMCP pins its pricing-policy version when the Run begins and stores the exact settlement request for retries. Changing current configuration cannot change an already-recorded charge. Text, voice, input transcription, memory extraction, and any billed attempts share the finite per-Run provider budget. Missing final usage holds accounting and new paid Runs until it can be verified; an operator cannot replace it with an estimate. Payload expiration does not remove pending accounting evidence or change the amount retried.