Confluent Rate Limits
Confluent enforces two distinct kinds of limit and it matters which one an agent hits. Request-rate and concurrency throttling returns 429 with headers; service quotas are resource COUNT ceilings (how many API keys, clusters, topics you may have) which surface as 402/400. Confluent publishes the throttling header contract precisely and the per-endpoint numeric rates not at all.
Confluent Rate Limits is the machine-readable rate-limit profile for Confluent on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 6 rate-limit definitions, measuring requests, concurrent-operations, connections-per-second, and api-keys.
The profile also includes response codes documented for throttled, quotaExceeded, quotaExceededKnownIssue, and serviceUnavailable.
Tagged areas include Rate Limiting, Quotas, Throttling, and Service Quotas.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.