Skip to main content
Dashboard sessions, CLI sessions, and API keys draw from one credit balance. Every metered response reports what it cost in X-Credits-Charged and the balance left in X-Credits-Remaining. See response conventions for the headers.

​
Reserves and charges

Before an operation runs, the API holds its reserve amount from your balance. When the operation finishes, the API charges the final amount and returns the rest of the hold. A failed operation returns the whole hold. If your balance is below the reserve, the request fails with 402 and X-Credits-Charged: 0, even when the balance would cover the final charge. A trend plan reserves 32 credits and charges 26, so a balance of 30 is not enough to start one.

​
Provider data

A request costs the fresh price only when the API fetches new data from the provider. A response served from cache, served stale, or shared with an identical in-flight request costs the cached price. Each page of a paginated endpoint is a separate request with its own charge. comments?all=true fetches up to five newest-first pages in one request and charges once. A capped crawl returns partial results; use continuation to read further.

​
Search and analysis

These operations charge a fixed amount whether or not the underlying data was cached.

​
Agent tool calls

When an agent fetches provider data during a run, each tool call uses the provider data prices above. Two operations exist only as agent tools: storyboard costs 1 credit cached or fresh, and frames cost 1 cached or 2 fresh. A tool call that reuses data already fetched in the same session costs 0.