Rb2B Rate Limits
RB2B publishes exactly one rate limit, and it is published inside an npm package rather than on a documentation site: 50 requests per second per endpoint on the Identity / Enrichment API. No limit is published for the OEM Partner API. No RateLimit-* / X-RateLimit-* / Retry-After header was observed on any response, so a client has no runtime signal — only the documented number and a 429 when it is crossed. The real throughput constraint in practice is the prepaid credit balance, not the per-second ceiling.
Rb2B Rate Limits is the machine-readable rate-limit profile for RB2B on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring requests_per_second.
Limit state is signalled in the rate_limit, remaining, reset, and retry_after response headers.
Tagged areas include Identity Resolution, Visitor Identification, B2B Data, Lead Generation, and Sales Intelligence.
rate_limitremainingresetretry_after
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.