Pricing

Everything is prepaid and priced per operation. There is no plan, no seat and no minimum spend: you fund a balance, each operation takes its price out of it, and the balance never goes below zero. An operation whose quoted price the balance cannot cover is refused before any work starts rather than billed afterwards.

How a charge happens

• Every operation creates a Run, and a Run is charged once — when the work happens. Reading it back later is free forever.
• A failed Run costs nothing. A partial Run charges for the items that arrived and nothing else. If the balance runs short while a multi-item Run is working, the completed items are charged in order up to the balance, the rest fail with insufficient_balance, and the Run ends partial.
• Almost every paid operation takes estimate, which answers with what the call would cost and creates no Run. The exceptions are POST /v1/trackers and POST /v1/trackers/{id}/refresh: they take no estimate and charge when called, so read the price on their reference entry first. See pricing and estimates.

Cached results

A result is cached when we already hold a snapshot of the subject younger than 24 hours, so the answer can be served without paying a vendor for it. Those calls cost 25% of the fresh price. Nothing about the response changes; the Run tells you whether it was cached and what you were charged.

The discount applies per piece of work rather than per call. A comments page with analyze=true is discounted on the page and on the analysis separately, each on its own cache clock, because those are separate pieces of work. Searches, scores and Tracker cycles are always a fresh fetch, so the discount never applies to them.

Starting out

A new account gets $5 of credit automatically, which expires after 90 days. After that you top up by card from $10 at a time. The balance never expires and is never charged for work that did not happen.

The price list

Grouped the way the API reference is grouped. Prices are per call unless the row says per page.

The same prices over MCP

The hosted MCP server bills identically — the tools are the same operations under different names. Free tools are omitted here; see the MCP guide for the full list.

What costs nothing

Reading is free. Once you have paid for a piece of work you can read it as often as you like — polling a running operation, fetching a finished result, walking the snapshots a Tracker has accumulated, listing change reports, checking your balance and reading your spend log all cost nothing and create no Run.

• GET /v1/research/{id} — Get a research
• GET /v1/research/{id}/videos — List a research's videos
• GET /v1/research/{id}/creators — List a research's creators
• GET /v1/research/{id}/hashtags — List a research's hashtags
• GET /v1/research/{id}/sounds — List a research's sounds
• GET /v1/research/{id}/digest — Read a research's digest
• GET /v1/creators/{platform}/{handle}/videos — List a creator's videos
• GET /v1/creators/{platform}/{handle}/snapshots — List a creator's snapshots
• GET /v1/trackers — List trackers
• GET /v1/trackers/{id} — Get a tracker
• PATCH /v1/trackers/{id} — Pause or resume a tracker
• DELETE /v1/trackers/{id} — Stop tracking
• GET /v1/trackers/{id}/snapshots — List a tracker's snapshots
• GET /v1/trackers/{id}/changes — List change reports
• GET /v1/runs — List runs
• GET /v1/runs/{id} — Get a run
• GET /v1/runs/{id}/items — List run items
• GET /v1/account/balance — Get balance
• GET /v1/account/usage — Get usage
• POST /v1/webhooks — Register a webhook endpoint
• GET /v1/webhooks — List webhook endpoints
• GET /v1/webhooks/{id} — Get a webhook endpoint
• DELETE /v1/webhooks/{id} — Delete a webhook endpoint
• POST /v1/webhooks/{id}/rotate — Rotate a signing secret
• GET /v1/webhooks/{id}/deliveries — List deliveries
• POST /v1/webhooks/{id}/deliveries/{deliveryId}/replay — Replay a delivery

Free operations still count against the per-key request limit, so a polling loop should still be a sensible one.

Worked examples

Three shapes of spend, with the arithmetic shown. Every unit price below is the same constant the API charges from.

Apart from the Tracker, none of these needs a commitment to find out: send estimate=true with the same parameters and you get the price back without a Run and without a charge. A Tracker takes no estimate over REST; the arithmetic above is its quote.