Request Costs

POST https://routing.dari.dev/v1/request-costs returns content-free pricing records for requests made with the same API key. Use the request UUID from your response ID (remove the chatcmpl- prefix for Chat Completions).

curl https://routing.dari.dev/v1/request-costs \
  -H "Authorization: Bearer $DARI_ROUTING_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"request_ids":["35fcb4c6-5902-40a7-adfe-e9289cab6855"]}'

The CLI provides the same lookup:

dari router request-costs 35fcb4c6-5902-40a7-adfe-e9289cab6855

Set DARI_ROUTING_API_KEY to the key that made the requests. This command does not create a key or perform inference.

Response

{
  "complete": true,
  "data": [{
    "request_id": "35fcb4c6-5902-40a7-adfe-e9289cab6855",
    "model_cost_usd": "0.0227905",
    "selected_model": "openai/gpt-6.1-sol",
    "provider_key_source": "subscription"
  }]
}

Send 1–1000 request UUIDs per lookup. Unknown IDs and IDs belonging to another key are omitted. complete: false means one or more requested IDs are not yet available; do not treat the returned records as a complete total. Telemetry is asynchronous: a request can be missing shortly after completion. A null cost means exact pricing is unavailable, not that the request was free. Responses must not be cached. model_cost_usd sums known, non-estimated provider-attempt reference costs. It is not an invoice or a subscription cash charge. It excludes sandbox charges, selector infrastructure, and Dari router fees. Failed provider attempts with explicit zero token usage contribute no cost; otherwise, incomplete or estimated attempt pricing returns null. Historical completed records without attempt metadata use their known provider reference cost.

Router APIs

Management API

Request Costs

Response

​Response

Response