specification: API Commons Rate Limits
specificationVersion: '0.1'
provider: CB Insights
providerId: cb-insights
generated: '2026-08-09'
method: searched
source: https://api-docs.cbinsights.com/docs/reference/rate_limiting/
created: '2026-08-09'
modified: '2026-08-09'
tags:
- Rate Limiting
- Market Intelligence
description: >-
  CB Insights publishes one rate limit that applies across all API calls, plus a separate,
  independent credit-consumption meter that is the real constraint on usage. The rate limit is a
  hard 100 requests per rolling one-second window; every data endpoint returns three IETF-style
  ratelimit-* headers so a client can self-pace. Exceeding it returns 429. The credit ledger is
  orthogonal — a call inside the rate limit still fails with 424 if the account has no credits left.
sources:
- https://api-docs.cbinsights.com/docs/reference/rate_limiting/
- https://api-docs.cbinsights.com/docs/reference/credit_model/
- https://api-docs.cbinsights.com/docs/reference/org_credit_model/
- https://api-docs.cbinsights.com/docs/endpoints/credits_endpoint/
headers:
  limit: ratelimit-limit
  remaining: ratelimit-remaining
  reset: ratelimit-reset
  creditsConsumed: x-cbinsights-credits-call-consumed
header_notes: >-
  ratelimit-reset is expressed as the seconds remaining in the current window.
  x-cbinsights-credits-call-consumed is returned on every v1 data response and carries the credit
  cost of that individual request.
responseCodes:
  throttled: 429
  creditExhausted: 424
limits:
- name: All API calls
  scope: account
  metric: requests_per_second
  limit: 100
  timeFrame: second
  window: rolling one-second window across all endpoints
  source: https://api-docs.cbinsights.com/docs/reference/rate_limiting/
quotas:
- name: Credit ledger
  metric: credits
  model: >-
    Consumption-metered. Each data request debits the account credit balance by an amount that
    varies by endpoint and datapack; the debit is reported per-response in
    x-cbinsights-credits-call-consumed. Balance and full ledger are readable via GET /v1/credits.
    Credit allotments are contractual and are not published.
  published_amount: false
  exhaustion_status: 424
  source: https://api-docs.cbinsights.com/docs/reference/credit_model/
- name: API trial allowance
  metric: entitlements
  published_amount: true
  values:
    companies: 25
    scouting_reports: 5
    chatcbi_messages: 5
  source: https://api-docs.cbinsights.com/portal/signup
pagination_limits:
- name: Organization lookup page size
  parameter: limit
  min: 1
  max: 100
  default: 10
  source: openapi/cb-insights-api-v2-openapi.json
- name: Credit log page size (v1)
  parameter: pageSize
  max: 1000
  default: 10
  source: https://api-docs.cbinsights.com/docs/endpoints/credits_endpoint/
- name: Deep-paging ceiling
  detail: >-
    totalHitsRelation is set to 'gte' once totalHits exceeds 10,000, indicating result sets are not
    fully enumerable beyond that depth.
  source: openapi/cb-insights-api-v2-openapi.json
gaps:
- The 429 status and the ratelimit-* headers are documented only in the v1 reference; the v2 Swagger
  contract declares neither, so a generated v2 client is throttle-blind.
- No Retry-After header is documented.
- No per-plan or per-endpoint rate differentiation is published.