Mage · Rate Limits

Mage Ai Rate Limits

The open-source, self-hosted Mage app does not document fixed public HTTP rate limits on its /api surface; effective throughput is governed by the resources of the host running the Mage server and its executor (local_python or Kubernetes). On Mage Pro, practical limits are expressed as plan allowances - monthly block runs (e.g. 15,000 on Team, 50,000 on Plus), AI token allowances, and compute hours - rather than per-minute request quotas. Specific per-endpoint throttling values are not reconciled in this artifact.

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

It captures 4 rate-limit definitions, measuring requests, block_runs, tokens, and compute_hours.

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

Tagged areas include Data Pipelines, Orchestration, ETL, Open Source, and Rate Limiting.

4 Limits Throttle: 429
Data PipelinesOrchestrationETLOpen SourceRate LimitingQuotasThrottling

Limits

Self-Hosted HTTP Requests deployment
requests
governed by host resources
Open-source self-hosted Mage publishes no fixed per-minute API rate limit.
Block Runs (Mage Pro) account
block_runs
see plan allowance
Monthly block-run allowances per Mage Pro tier (e.g. 15,000 Team, 50,000 Plus).
AI Tokens (Mage Pro) account
tokens
see plan allowance
Monthly AI token allowance per Mage Pro tier.
Compute Hours (Mage Pro) account
compute_hours
usage-based
Kubernetes-executor compute billed per hour; not a hard request limit.

Policies

Resource-Bound Throughput
Self-hosted API throughput scales with host CPU/memory and executor type.
Plan Allowances
Mage Pro enforces block-run and AI-token allowances per subscription tier.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After when throttled.

Sources