Arize AI

Arize AI

@arize.bsky.social

Arize is an AI engineering platform focused on evaluation and observability. It helps engineers develop, evaluate, and observe AI applications and agents.

120 followers31 following487 posts

AI cost optimization starts with knowing where costs are coming from. At TheFork, Arize AX tracing is helping the team get clearer cost signals and identify opportunities to improve efficiency. Learn how to reduce LLM costs without sacrificing quality: arize.com/blog/how-to...

arize.comHow to reduce LLM costs without sacrificing qualityTrace where your AI budget goes, identify the requests that do not justify their spend, and validate lower-cost alternatives with Arize AX.

For @siemenssoftware, trust in GenAI starts with visibility into system performance. With Arize AX evals and monitoring, the team can spot unexpected agent behavior and investigate issues as they scale.

Why make an LLM read thousands of spans to count errors? In our benchmark, querying traces with SQL + code mode cost ~17x less than fetching spans page by page. See how @ArizePhoenix MCP does it, live in Claude Code and Cursor. Register here: luma.com/arizeai-que...

luma.comInside Phoenix MCP: how remote MCP, SQL, and code mode let agents query traces · LumaYou ask a coding agent a simple observability question: how many spans failed yesterday, which tool was called most, where latency spiked. Without the right…

Claude can refuse legitimate security work because it looks dangerous. But in a test, a fake permission claim in CLAUDE.md convinced it to help bypass login and dump a database. Somehow we've made agent permissions both too strict and too gullible.

But models can't verify who you are, or even whether the instructions they're following came from you. We already know how to do authorization in software and it's becoming clear that agents need those same checks in the harness before tools execute. Read more: arize.com/blog/ai-age...

arize.comAI agent permissions: Why agents don't know what you're allowed to doWhy AI agents refuse authorized work or accept false authority, and how tool-level permission checks and tracing help you build safer agents.

A neutral instruction to answer without extra commentary reduced output tokens by 13-74% without hurting accuracy. But Opus 5.5 and GPT-6.1 increased their hidden thinking, showing why measuring output tokens alone can misrepresent inference costs.

Your LLM bill went up. Cost Agent finds out why. Introducing Cost Agent in Arize AX: a managed agent that finds what’s driving LLM spend, quantifies the impact, and recommends what to fix. One analysis found 35–40% estimated monthly savings. Learn more: arize.com/blog/arize-...

Ask an LLM judge a yes/no question and it often writes you a paragraph. Then you parse it for the answer. Jev-as-a-Judge in Arize AX answers in types: booleans, choices and rubric scores, each with a confidence, several questions per call. Set it up: arize.com/docs/ax/eva...

Arize AX now renders videos added to spans when you view traces. Great for digging into issues in your AI video pipelines that your evals, or managed agents like Signal, have surfaced.

For all you Codex fans out there, we've just added support for Codex as the harness for your managed agents. Configure your managed agents with Codex as the harness, select your models, skills, attach repos, and define your task. Then let your managed agent rip!

Arize AI reposted

Laurie Voss, co-founder of npm and now Head of Developer Relations at Arize AI, says code review is being quietly replaced by automated verification harnesses.

OpenTelemetry’s GenAI semantic conventions are becoming a common way for frameworks and agent platforms to describe model calls, tools, retrieval, token usage, and more. Arize AX now offers native support, so gen_ai.* spans arrive as structured AI traces. Learn more: arize.com/blog/arize-...

View full thread

There’s some useful history here. We created OpenInference at Arize before the broader OpenTelemetry GenAI conventions were mature enough for dependable AI-specific instrumentation. Today, more frameworks emit gen_ai.* telemetry natively, so the two increasingly need to work together.

A practical rule: - Use OpenInference when you control instrumentation. - Use OpenTelemetry GenAI conventions when your framework already emits them or you primarily control the OTLP export. - Mixed environment? AX supports both. Learn more: arize.com/blog/arize-...

OpenTelemetry’s GenAI semantic conventions are becoming a common way for frameworks and agent platforms to describe model calls, tools, retrieval, token usage, and more. Arize AX now offers native support, so gen_ai.* spans arrive as structured AI traces. Learn more: arize.com/blog/arize-...

That matters when you don’t control the runtime. If a managed agent platform already emits OpenTelemetry GenAI telemetry, you can send it to AX over OTLP and use it for tracing, evals, token analysis, and debugging without maintaining a custom conversion processor.

The EU AI Act turns principles like fairness, transparency, human oversight, and robustness into evidence product and engineering teams may need to produce for a specific AI system over time. Here’s what that means for developers: arize.com/blog/demyst...

arize.comDemystifying the EU AI Act for AI product and engineering teamsAn engineering guide to turning EU AI Act principles into traces, evaluations, annotations, and release evidence product and engineering teams can actually demonstrate.
View full thread

Documentation works better when your system generates it during normal operation. Traces preserve what happened. Annotations record human review. Evals measure behavior. CI records whether changes passed your release criteria.

Here's a practical place to start: - Pick one high-risk use case. - Identify the principle you would struggle to demonstrate today. - Instrument the workflow, define the metric and owner, then connect the result to your release process. Full engineering guide: arize.com/blog/demyst...

arize.comDemystifying the EU AI Act for AI product and engineering teamsAn engineering guide to turning EU AI Act principles into traces, evaluations, annotations, and release evidence product and engineering teams can actually demonstrate.

The EU AI Act turns principles like fairness, transparency, human oversight, and robustness into evidence product and engineering teams may need to produce for a specific AI system over time. Here’s what that means for developers: arize.com/blog/demyst...

arize.comDemystifying the EU AI Act for AI product and engineering teamsAn engineering guide to turning EU AI Act principles into traces, evaluations, annotations, and release evidence product and engineering teams can actually demonstrate.

Much of that evidence already comes from normal AI engineering workflows: traces, evals, annotations, CI, and audit logs. For each requirement, define the metric, owner, threshold, review path, and release consequence.

Be careful with AI-generated evaluation scores. If an LLM judge measures fairness or bias, calibrate it against human reviewers on representative examples and inspect where they disagree. The metric needs evidence behind it, too.

@HamelHusain keeps stopping eval reviews for the same reason: the model isn't broken, but the product is. In part 2 of our series Rise of the Agent Engineer, Hamel walks through why ambiguous inputs, generic metrics, and disconnected reviews make AI evaluations misleading, and how to fix them.

What if your agents got better every time they failed? Today, we’re launching Signal. It continuously reviews production traces, finds issues, and turns them into an investigation with evidence, root cause, and a proposed fix. Your engineers decide what ships. arize.com/blog/from-s...

Want to master the full workflow of shipping reliable AI agents? Laurie's workshop from AI Engineer World's Fair, "Evaluating and Shipping AI Agents That Work," is now a free, self-paced course on Arize University. Earn a certificate you can share on LinkedIn by completing 13 episodes that cover:

Two AI observability lessons from @bookingcom: - An agent latency spike came from a model running without the appropriate service tier. - Multi-turn eval scores fell because long URLs were being added back into the conversation history, causing the context to balloon.

View full thread

The broader playbook on agent observability from @bookingcom: - Trace model calls, retrieval, tools, guardrails, and fallbacks - Monitor quality alongside latency and token usage - Pull real failures into datasets for experimentation - Centralize sampling, PII redaction, and telemetry routing

Two AI observability lessons from @bookingcom: - An agent latency spike came from a model running without the appropriate service tier. - Multi-turn eval scores fell because long URLs were being added back into the conversation history, causing the context to balloon.

Both problems became much easier to fix once the team could connect production signals to individual traces, configurations, and conversations.

Claude Opus 5 is available in Arize AX, supported across Anthropic API, AWS Bedrock, and Vertex AI! Opus 5 brings major improvements for long-running agents in coding and professional work. Instrument, evaluate, and improve your agents with day 0 support for Anthropic's newest model.

Token price tells you what a model costs to call. It does not tell you what it costs to finish the job. Arize and @FireworksAI_HQ benchmarked 10 models across 2,400 agent runs, including Kimi K3.

In his tests, Arize's Head of DevRel @seldo found: • Kimi K3 nearly matched GPT-5.5 overall • Different models won on different task types • Routing improved cost and coverage • Retries and silent failures changed the economics completely

Gemini 3.6 Flash and Gemini 3.5 Flash-lite are now available in Arize AX! Both models are supported on direct Gemini and Vertex AI providers with configurable thinking levels, 65K max output tokens, and audio file input.