Anonymous
$0
Inspect a bounded sample. No account, no key: make the first request.
- Requests per minute
- 60
- Requests per month
- No monthly cap
- Rows per page
- 100
- History window
- about 13 months
- Keys
- None
- Research API and MCP
- No
Pay for volume and history, not for access.
Anonymous reads, a free key, Pro and Team. Every limit is a number you can count before you call: requests, rows per page and the history window.
Getting a key never lowers a limit. Pro is $49 a month, with hard caps and no overage charge.
Four ways in
Pick the one that matches the job.
Free key
$0
Build and test a small integration against your own key.
- Requests per minute
- 60
- Requests per month
- 5,000 / month
- Rows per page
- 500
- History window
- Up to 2 years, where retained
- Keys
- 1
- Research API and MCP
- No
Pro
$49 / month
Run a recurring workflow at volume, with the full retained history.
- Requests per minute
- 300
- Requests per month
- 100,000 / month
- Rows per page
- 5,000
- History window
- Full retained archive
- Keys
- 3
- Research API and MCP
- Included
See Pro
Checking Pro availability…
Team
Contact us
Shared admin, multiple keys, support and agreed usage rights.
- Limits
- Agreed in writing
- Keys
- Several, shared admin
- Usage rights
- Agreed
- Support
- Included
Limits are hard caps with no overage charge: reaching one returns a 429 that says which limit and when to retry, never a bill. Anonymous use has no monthly counter. It is bounded by the per-IP rate, a five-minute edge cache, the page size and the history window.
Metering
What counts as a request.
- One HTTP call to
/api/datasetsis one request, whether it returns one row or a full page. Rows per page (the same cap applies to a CSV export) limit how much a single request can return. - Following
next_cursorto the next page is another request. A change-feed poll is one request per poll. - MCP tool calls draw from the same monthly allowance as the HTTP API. MCP is the same operations, reached as tools.
- A keyed call is never served from a shared cache. Anonymous reads are cached at the edge for five minutes, so a repeat of the same URL inside that window does not reach the database.
- Your counts for today and this month are returned by
/api/usagewith your key.
Upgrading
What you get when you upgrade.
Anonymous → Free key
- 500 rows a page instead of 100
- Up to 2 years, where retained of history instead of about 13 months
- Your own usage counts at /api/usage, so you can see what you spend
- The same per-minute rate as anonymous (60); a key never lowers a limit
Free key → Pro
- 300 requests a minute and 100,000 / month
- 5,000 rows a page, as JSON or CSV
- Full retained archive instead of Up to 2 years, where retained
- The research API and MCP, and up to 3 keys
Pro → Team
- Shared administration across several keys
- Support and a named contact
- Usage and redistribution rights agreed in writing
FAQ
Before you choose.
- Is the archive really two years deep?
- Do not take a number from a pricing page for it. The history window above is how far back a tier is allowed to read; how far back the record actually reaches differs by dataset and source. The measured earliest retained date, record counts and missed collection windows are on the coverage page, generated from the archive itself.
- Why does a free key have a monthly cap when anonymous does not?
- A keyed call is uncached and reads the database directly, so it is the one we meter. Anonymous reads are cached at the edge and bounded by the per-IP rate, page size and history window instead. A free key is never slower than anonymous: 60 requests a minute against 60.
- Can I be billed for going over?
- No. Limits are hard caps. At the cap the API answers 429 with
Retry-After; there is no overage rate. - What does Team include?
- Shared administration, several keys, support and usage rights agreed in writing. There is no public price or limit table for it; contact us with what you need.
- Where are the technical details?
- Endpoints, parameters, errors and the changelog are on the API page.