- Was it the prompt, the model, the tool call, or the underlying infrastructure?
- Did a database timeout cause the agent to return a fallback response?
- Is the cost spike from a model change or from a retry loop caused by a failing downstream service?
Who AgentVista is for
AgentVista is built for solo founders and small teams (typically 2–10 people) shipping AI-native products. If AI agents are core to your product — not a side feature — and you don’t have the time or budget to run two separate observability stacks, AgentVista is for you.What AgentVista does
Traces
Every agent run becomes a trace. Child spans capture LLM calls, tool invocations, and sub-agent delegation — including spans from your infrastructure services in the same waterfall.
Metrics
Track token usage, cost per run, latency, success rate, CPU, memory, request rate, and error rate — all in one dashboard, attributed to the same workflow.
Logs
Ingest prompt/completion pairs, tool call inputs and outputs, and standard application logs. Click from any log line to the trace it belongs to.
Cost tracking
See the full cost of a workflow: LLM token spend plus infrastructure compute, broken down by agent, by feature, and by customer.
Outcome signals
Define what success means for each agent. Track success rates over time, by agent, by model, and by prompt version. Correlate failures back to their root cause.
Alerts
Set threshold-based and composite alerts on any combination of AI metrics, infrastructure metrics, and outcome signals — delivered by email or webhook.
Get started
Quick Start
Send your first trace in under 5 minutes.
Install the SDK
Install the Python SDK and explore all tracing APIs.
API reference
Explore REST endpoints for ingestion and querying.
Traces and spans
Understand how AgentVista models agent runs and infrastructure calls.