Crunchbase · Rate Limits

Crunchbase Data Rate Limits

Crunchbase documents a single API-wide rate limit of 200 calls per minute across the Data API endpoints, applied to protect platform reliability and performance. Beyond that per-minute cap, usage is governed by the terms of the account's licence (Enterprise, Applications, or Basic) rather than by published per-endpoint quotas. Response sizes are separately bounded: search returns 50 items by default and 1000 maximum, autocomplete caps at 25, and a card included inline on an entity lookup returns at most 100 items. Keyset cursors (after_id / before_id) traverse anything larger.

Crunchbase Data Rate Limits is the machine-readable rate-limit profile for Crunchbase on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 5 rate-limit definitions, measuring requests and items.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, httpsRequired, and unauthorized.

Tagged areas include Company Data, Funding Data, Web Intelligence, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Company DataFunding DataWeb IntelligenceRate LimitingQuotas

Limits

API Calls account
requests
200 per minute
Documented API-wide rate limit across all Data API endpoints, per API key.
Search Result Size request
items
50 default / 1000 max
Per-request result cap on POST /data/searches/{collection}; page with after_id / before_id. The real ceiling within 1000 depends on the licence.
Autocomplete Result Size request
items
10 default / 25 max
The limit query parameter on GET /data/autocompletes maxes at 25. No pagination.
Entity Card Inline Items request
items
100 per card
Cards included via card_ids on an entity lookup return at most 100 items; use GET /data/entities/{collection}/{entity_id}/cards/{card_id} with a keyset cursor for more.
Licence Call Allowance account
requests
per contract
Total call volume is governed by the Enterprise / Applications / Basic licence terms; not publicly published.

Policies

HTTPS Required
All API requests must use HTTPS; non-HTTPS requests are rejected with HTTP 426.
Keyset Pagination
Search, card and deleted-entity endpoints use keyset cursors (after_id / before_id over entity UUIDs) so results stay stable as the graph changes.
Backoff Strategy
Clients should stay under 200 calls/minute and implement exponential backoff with jitter on 429. Because no Retry-After is returned, the backoff schedule has to be chosen by the client rather than honoured from the response.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/crunchbase-data-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.