Phoenix Rate Limits
Rate limits for the Arize Phoenix REST API vary by deployment type and plan. Self-hosted deployments have no enforced API rate limits beyond hardware capacity. The managed Arize AX cloud service enforces monthly volume limits on trace spans and data ingestion, with additional per-request limits applied at the HTTP layer. Authentication is required for all API calls via bearer token (API key).
Phoenix Rate Limits is the machine-readable rate-limit profile for Arize Phoenix on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions.
Tagged areas include LLM Observability, AI Evaluation, OpenTelemetry, Tracing, and LLMOps.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/phoenix-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.