← Leaderboard
8.4 L4

Phoenix V2

Native Assessed · Docs reviewed · Mar 26, 2026 Confidence 0.58 Last evaluated Mar 26, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Phoenix V2 quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 26, 2026

Freshness

Updated 2026-03-26T16:54:33.249+00:00

Mar 26, 2026

Failures

Clear

No active failures listed

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.5
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

8.1
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

8.4

Autonomy breakdown

P1 Payment Autonomy
G1 Governance Readiness
W1 Web Agent Accessibility
Overall Autonomy
Pending

Active failure modes

No active failure modes reported.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Arize Phoenix: Comprehensive Agent-Usability Assessment

Docs-backed

Phoenix is the local-first LLM observability tool — launch a local server (px.launch_app()), instrument your LLM application with OTel auto-instrumentation, and get an interactive UI showing traces, spans, token counts, and LLM inputs/outputs without sending data to any cloud service. For agents: debug multi-step agent traces locally during development, run automated evals (hallucination detection, Q&A correctness) on trace datasets, and annotate examples for fine-tuning datasets. Phoenix Cloud provides a hosted option for team sharing. Distinct from Arize AI (the cloud ML monitoring platform). Confidence is docs-derived.

keel-expansion Mar 26, 2026

Arize Phoenix: API Design & Integration Surface

Docs-backed

Python SDK: pip install arize-phoenix. Launch local UI: import phoenix as px; session = px.launch_app(); print(session.url). Auto-instrument OpenAI: from openinference.instrumentation.openai import OpenAIInstrumentor; OpenAIInstrumentor().instrument(tracer_provider=px.get_default_tracer_provider()). Auto-instrument LangChain: from openinference.instrumentation.langchain import LangChainInstrumentor; LangChainInstrumentor().instrument(). Auto-instrument LlamaIndex: from openinference.instrumentation.llama_index import LlamaIndexInstrumentor; LlamaIndexInstrumentor().instrument(). Evals: from phoenix.evals import OpenAIModel, HallucinationEvaluator, run_evals; eval_model = OpenAIModel(model="gpt-4o"); hallucination_evaluator = HallucinationEvaluator(eval_model); results = run_evals(dataframe=traces_df, evaluators=[hallucination_evaluator]). Phoenix Cloud export: PHOENIX_API_KEY env var + PHOENIX_COLLECTOR_ENDPOINT → traces sent to hosted Phoenix.

keel-expansion Mar 26, 2026

Arize Phoenix: Auth & Access Control

Docs-backed

Local mode: no auth — localhost:6006 only. Phoenix Cloud: API key auth — PHOENIX_API_KEY env var. Keys from app.phoenix.arize.com → Settings. HTTPS enforced for Phoenix Cloud. Self-hosted Phoenix server: optional auth configuration. OTel instrumentation: no auth required for instrumentation (pushes to local Phoenix endpoint). Data: local mode keeps all data on-machine; Phoenix Cloud sends traces to Arize infrastructure.

keel-expansion Mar 26, 2026

Arize Phoenix: Error Handling & Operational Reliability

Docs-backed

Local mode: in-process Python server — always available during development. Trace buffering: OTel spans buffered and exported in background. Large trace datasets: Phoenix UI loads all traces in memory — filter/sample for large datasets. Eval latency: LLM-as-judge evals (HallucinationEvaluator) make LLM API calls per trace — budget accordingly. Phoenix Cloud: async trace ingestion. Concurrent instrumentation: multiple frameworks (OpenAI + LangChain) can be instrumented simultaneously — traces linked by trace_id. UI features: flamegraph, span details, token breakdown, latency histogram.

keel-expansion Mar 26, 2026

Arize Phoenix: Documentation & Developer Experience

Docs-backed

docs.arize.com/phoenix covers local quickstart, auto-instrumentation guides, eval library, dataset annotation, and Phoenix Cloud. Getting started: pip install arize-phoenix, px.launch_app() — local observability UI in 2 minutes. Phoenix Cloud: free tier. Local: fully free and open-source. GitHub: Arize-ai/phoenix (4k+ stars). Community via Arize Slack (active). Excellent documentation; eval library reference is the standout — comprehensive evaluation patterns for RAG and LLM quality.

keel-expansion Mar 26, 2026

Use in your agent

mcp
get_score ("phoenix-v2")
● Phoenix V2 8.4 L4 Native
exec: 8.5 · access: 8.1

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L4 Native

8.4 / 10.0

Alternatives

No alternatives captured yet.