OpenMeter · Rate Limits

Openmeter Rate Limits

Self-hosted open-source OpenMeter imposes no vendor rate limits - throughput is bounded only by the infrastructure you run (ingestion, ClickHouse, Kafka). OpenMeter Cloud enforces plan-dependent limits on API request rate and on ingested/metered event volume; batch CloudEvents ingestion is the recommended path for high-throughput event streams. Specific per-tier request-per-second and monthly event ceilings are set on the OpenMeter pricing/plan pages and are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests and events.

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

Tagged areas include Usage Metering, Billing, Entitlements, CloudEvents, and Open Source.

3 Limits Throttle: 429
Usage MeteringBillingEntitlementsCloudEventsOpen SourceRate LimitingQuotasThrottling

Limits

API Requests account
requests
see provider documentation
Cloud request-rate limits vary by plan; open source is unlimited (infra-bound).
Ingested Events account
events
see plan allowance
Metered/ingested events counted against the monthly plan allowance on Cloud.
Batch Ingestion request
events
batch payload size bound
Prefer application/cloudevents-batch+json to ingest many events per request.

Policies

Tiered Limits
Request-rate and event-volume ceilings rise across Cloud Free, Usage-Based, and Enterprise tiers.
Self-Hosted Unlimited
The open-source deployment has no vendor-imposed limits; throughput is bounded by your own infrastructure.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429.

Sources