Agent Surface

Tooling Catalog

Evaluation and Observability

AI evals, traces, monitoring, guardrails, policy, and security tooling

Last verified 2026-09-24

Use these when agent behavior must be measurable, regressions must be caught, or untrusted inputs and sensitive data need explicit controls.

Evaluation and Observability

Keep this category AI-specific. General monitoring tools are only relevant as backends when paired with GenAI instrumentation.

First check whether your agent framework already ships an exporter for the backend. Framework-native exporters mean tracing is configuration rather than instrumentation work; Mastra, for one, ships exporters for Arize, Arthur, Braintrust, Datadog, Laminar, Langfuse, LangSmith, PostHog, and Sentry alongside plain OpenTelemetry. Check your framework's exporter list before you shortlist on features alone.

ToolWebsiteWhat it is forTierNotes
Braintrustbraintrust.devAI observability, , datasets, experiments, prompts, and production monitoringCoreStrong default for serious eval loops and regression testing.
Langfuselangfuse.com tracing, prompt management, evals, datasets, and analyticsCoreStrong open-source option with broad framework integrations.
LangSmithdocs.smith.langchain.comLangChain and LangGraph tracing, evals, datasets, and deployment feedbackConditionalStrong when using LangChain or LangGraph.
Arize Phoenixarize.comOpen-source LLM observability, tracing, evals, and prompt experimentsCoreStrong OpenTelemetry/OpenInference-aligned option, and a common framework-native exporter target.
Laminarlaminar.shOpen-source agent observability with traces, failure clustering, evals, and a CLI/MCP pathConditionalApache-2.0 and self-hostable via Docker or Helm. Notable for turning error clusters into eval datasets, which closes the trace-to-regression-test loop rather than stopping at dashboards.
Arthurarthur.aiAgentic tracing, automated evaluations, , and AI governance in one control planeConditionalFits when governance, ownership, and risk scoring are the requirement rather than developer debugging alone; an open-source arthur-engine exists for the evaluation and guardrail layer.
Promptfoopromptfoo.devCLI-first prompt, model, , agent, and evaluationsCoreGood for CI-friendly evals and adversarial testing.
RAGASdocs.ragas.ioRAG and agent evaluation metricsConditionalUseful for retrieval quality loops; avoid treating metrics as absolute truth.
DeepEvaldeepeval.comLLM eval framework for RAG, agents, chatbots, safety, and CI testsConditionalGood Python option for test-like evals and synthetic data.
Opikcomet.comOpen-source LLM observability, evaluation, prompt tracking, and agent optimizationConditionalGood open-source option alongside Langfuse and Phoenix.
Weights & Biases Weaveweave-docs.wandb.aiLLM traces, evals, datasets, and experiment trackingConditionalGood if the team already uses W&B.
Heliconedocs.helicone.aiLLM gateway observability, caching, costs, and logsConditionalUseful when lightweight model-call logging and cost visibility are enough.
PostHog LLM Observabilityposthog.comLLM analytics, cost tracking, and product-level observabilityConditionalRelevant when LLM telemetry should sit next to product analytics and feature flags, and now a first-class exporter target in agent frameworks rather than a manual integration.
MLflow Tracingmlflow.orgOpenTelemetry-compatible tracing for LLM and agent applicationsConditionalGood if the team already uses MLflow or wants self-hosted GenAI traces that can feed eval datasets.
New Relic AI Monitoringdocs.newrelic.comAPM-backed AI monitoring for LLM calls, , latency, , cost, and feedbackConditionalUse when New Relic is already the production observability system; keep AI evals in a dedicated eval loop.
SigNoz LLM Observabilitysignoz.ioOpenTelemetry-native LLM observability integrations and dashboardsConditionalGood for open-source or self-hosted teams that want GenAI telemetry beside traces, logs, and metrics.
AgentOpsdocs.agentops.aiAgent session tracing, replay, and analyticsWatchRelevant for agent-specific debugging; evaluate ecosystem fit.

Guardrails, Security, and Policy Tools

Use these when agents read untrusted content, handle user data, call write tools, or operate in regulated environments. These tools do not replace product-level permission design; they help enforce and observe it.

ToolWebsiteWhat it is forTierNotes
Guardrails AIguardrailsai.comValidation, structured-output checks, and guardrail for LLM appsConditionalGood when output shape, policy checks, or validation failures need first-class handling.
NeMo Guardrailsdocs.nvidia.comProgrammable guardrails and dialog controls for LLM applicationsConditionalUseful in enterprise/NVIDIA-aligned stacks or policy-heavy conversational systems.
Lakeradocs.lakera.aiPrompt-injection and LLM security protectionConditionalConsider for agents browsing or ingesting hostile/untrusted web content.
Llama Guardllama.comSafety classification model familyConditionalUseful as a self-hostable or model-based safety classifier, depending on deployment needs.
Microsoft Presidiomicrosoft.github.ioPII detection, redaction, and anonymizationConditionalPractical for logs, traces, eval datasets, and tool outputs that may contain sensitive data.
Pangea AI Guardpangea.cloudAI security guardrail for prompt, response, and data protectionWatchTrack for teams already using Pangea security services.
Superagentdocs.superagent.shGuardrails, PII, prompt-injection, and verification tooling surfaced by the AI registryWatchWorth evaluating as the AI SDK ecosystem adds packaged security tools.

Public Readiness Scanners

External, deployed-site scanners such as Is Agentic, Ora, Cloudflare Agent Readiness, Google Lighthouse's Agentic Browsing category, and Shopify's product-page audit check what an outside agent can observe right now; they complement rather than replace a repository-level Surface audit. See Public Readiness Scanners for coverage, APIs, and how to interpret each one's findings.

Sources are linked inline.

On this page