Arize Phoenix
Arize Phoenix is an open-source AI observability and evaluation platform built on OpenTelemetry, enabling developers to trace, evaluate, and debug LLM applications in production or locally. Phoenix exposes a REST API for programmatically ingesting spans and traces, managing datasets, running experiments, submitting annotations, and querying evaluation results. The platform supports a wide range of LLM frameworks including LangChain, LlamaIndex, OpenAI, Anthropic, and CrewAI through auto-instrumentation. Phoenix can be self-hosted in a single command or used as a managed cloud service (Arize AX), with authentication via API keys and OAuth2/OIDC for enterprise deployments.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Arize Phoenix the way a machine reads it — 38 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Arize Phoenix scores 51.0/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Arize Phoenix
Each block below is one kind of artifact we hold for Arize Phoenix. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 17
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Arize Phoenix annotation_configs API
The annotation_configs API from Arize Phoenix — 3 operation(s) for annotation_configs.
Arize Phoenix annotations API
The annotations API from Arize Phoenix — 3 operation(s) for annotations.
Arize Phoenix Arize Phoenix Version API
The Arize Phoenix Version API from Arize Phoenix — 1 operation(s) for arize phoenix version.
Arize Phoenix Auth API
The Auth API from Arize Phoenix — 6 operation(s) for auth.
Arize Phoenix chat API
The chat API from Arize Phoenix — 2 operation(s) for chat.
Arize Phoenix datasets API
The datasets API from Arize Phoenix — 9 operation(s) for datasets.
Arize Phoenix experiments API
The experiments API from Arize Phoenix — 8 operation(s) for experiments.
Arize Phoenix Healthz API
The Healthz API from Arize Phoenix — 1 operation(s) for healthz.
Arize Phoenix Oauth2 API
The Oauth2 API from Arize Phoenix — 2 operation(s) for oauth2.
Arize Phoenix projects API
The projects API from Arize Phoenix — 2 operation(s) for projects.
Arize Phoenix prompts API
The prompts API from Arize Phoenix — 8 operation(s) for prompts.
Arize Phoenix Readyz API
The Readyz API from Arize Phoenix — 1 operation(s) for readyz.
Arize Phoenix secrets API
The secrets API from Arize Phoenix — 1 operation(s) for secrets.
Arize Phoenix sessions API
The sessions API from Arize Phoenix — 5 operation(s) for sessions.
Arize Phoenix spans API
The spans API from Arize Phoenix — 6 operation(s) for spans.
Arize Phoenix traces API
The traces API from Arize Phoenix — 4 operation(s) for traces.
Arize Phoenix users API
The users API from Arize Phoenix — 3 operation(s) for users.
Scroll within the panel for all 17 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Phoenix Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Phoenix Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Phoenix Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Arize Phoenix API Rules
SPECTRALJSON Schema 10
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AnnotateSpansRequestBody
JSON SCHEMAAnnotateSpansResponseBody
JSON SCHEMAAnnotationResult
JSON SCHEMADataset
JSON SCHEMADatasetVersion
JSON SCHEMAExperiment
JSON SCHEMAExperimentRun
JSON SCHEMAProject
JSON SCHEMASpan
JSON SCHEMASpanAnnotation
JSON SCHEMAScroll within the panel for all 10 ·
Examples 4
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Phoenix Create Span Example
EXAMPLESecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Arize Phoenix — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/phoenix · machine-readable index on apis.io