specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Datafiniti
providerId: datafiniti
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Business Data
  - Data as a Service
  - Rate Limiting
description: Datafiniti does not publish numeric rate limits on its public website. Throttling
  behavior, per-key concurrency, and download caps are documented inside the gated developer portal
  and tied to the customer's subscription tier. Consumers should consult the portal docs after
  sign-up. Record volume is the dominant cost driver, not request rate.
sources:
  - https://datafiniti.co
  - https://portal.datafiniti.co
notes: No public rate limit page; numbers are tier-dependent and visible only after portal sign-up.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Subscription-tier request rate
    scope: api-key
    metric: requests_per_minute
    limit: see datafiniti portal documentation
    notes: Per-tier RPM is set at the customer's subscription level; not published publicly.
  - name: Subscription-tier monthly record quota
    scope: account
    metric: records_per_month
    limit: see datafiniti portal documentation
    notes: Record allowance is the primary meter and is set per subscription.
policies:
  - name: Backoff Strategy
    description: On HTTP 429, callers should back off and retry with exponential delay and jitter,
      honoring any Retry-After header returned by the API.
  - name: Tier-Bound Quotas
    description: Quotas scale with the subscription tier negotiated through the portal or sales.
      Upgrades raise both record allowance and request rate.
  - name: Record Volume Drives Cost
    description: Because pricing scales by record volume, callers should batch and filter
      server-side rather than over-fetching.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com