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: APIToolkit (Monoscope) providerId: apitoolkit 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-22' tags: - API Monitoring - Observability - Rate Limiting - Quotas - Throttling description: >- Machine-readable rate limits for the Monoscope Platform REST API as published at https://monoscope.tech/docs/api-reference/getting-started/rate-limits/. Limits are measured in requests per minute, are tiered by plan, and are signaled via X-RateLimit-* headers. headers: limit: X-RateLimit-Limit remaining: X-RateLimit-Remaining reset: X-RateLimit-Reset retryAfter: Retry-After responseCodes: throttled: 429 quotaExceeded: 429 limits: - tier: free name: Free Tier API scope: api-key metric: requests_per_minute limit: 60 burst: 10 timeFrame: minute applies: - Monoscope Platform API - tier: pro name: Pro Tier API scope: api-key metric: requests_per_minute limit: 300 burst: 50 timeFrame: minute applies: - Monoscope Platform API - tier: enterprise name: Enterprise Tier API scope: contract metric: requests_per_minute limit: -1 timeFrame: minute applies: - Monoscope Platform API ingestion: - tier: monoscope-cloud name: Cloud Included Events metric: events_per_month limit: 20000000 overage: price: '1.00' unit: 1000000 currency: USD - tier: monoscope-cloud-s3 name: Cloud + S3 Included Events metric: events_per_month limit: 100000000 overage: price: '1.00' unit: 1000000 currency: USD - tier: self-hosted-community name: Self-Hosted Community Events metric: events_per_month limit: -1 - tier: self-hosted-enterprise name: Self-Hosted Enterprise Events metric: events_per_month limit: -1 policies: - name: Monitor X-RateLimit-Remaining description: Clients should proactively monitor X-RateLimit-Remaining to anticipate throttling. - name: Exponential Backoff description: On 429, implement exponential backoff and retry after the X-RateLimit-Reset timestamp. - name: Broader Time Ranges description: Optimize queries by using broader time ranges rather than many narrow requests. - name: Per-Key Scope description: Rate limits and event allowances apply per project-scoped API key. maintainers: - FN: Kin Lane email: info@apievangelist.com