Skip to main content
Apiosk shows a price before a data purchase. The displayed total is the most the request may cost. You approve that ceiling once; the finished run reports the actual charge and the source behind it.

​
The buying flow

  1. Browse sources or ask a question. Browsing and planning are free.
  2. Review the plan and its total price ceiling.
  3. Approve the plan in the app or MCP card. With the API, send max_spend to authorize an automatic run or call the plan’s run endpoint.
  4. Apiosk reserves each source call before dispatching it. Settled charges and any funds still held appear separately in the run’s usage.
  5. Read the sourced result and final charge. Unused reserved money is released. A call that did not deliver data is refunded or held for reconciliation if its outcome is still unknown.
Prices and balances are shown in USD. API amounts include both a decimal amount and an exact amount_micro_usd. The catalogue’s price is the buyer total for that operation; there is no extra fee to add to the displayed quote.

​
Which balance pays?

An API key also has its own per-request and monthly limits. An assistant connection has a per-request and daily limit. A limit or balance refusal means the purchase did not start. In the buyer API, HTTP 402 with insufficient_balance or spend_limit_exceeded asks you to fund the balance or change the relevant limit. For exact fields, see Balance and usage, Ask, and Runs.