01
The action sequence
Tool calls, decisions, and messages, in order. A failed agent is often a step in the middle, not the final reply.
Agent monitoring
AI agent monitoring is a timeline of actions, plus a note when the pattern breaks. AgentTracer keeps that timeline, emails a weekly digest, and sends anomaly alerts. Fully managed: no infrastructure to run. One API key and you're tracing.
Agent monitoring covers five things. The first is the story of the run. The other four are how that story goes wrong: a loop of errors, a burst of calls, a quiet agent, or a tool you did not want called.
01
Tool calls, decisions, and messages, in order. A failed agent is often a step in the middle, not the final reply.
02
The same error, over and over, is a loop. Record an error event each time it happens so the rate is visible.
03
A cost spike usually arrives as more model and tool calls. Volume is the signal you can see without a price list.
04
An agent that was busy and then sends nothing is its own incident. The missing timeline is the alert.
05
Refunds, sends, deletes, and other tools that leave your system. Put the call on the timeline. A monitor cannot guess which tools matter.
01
Send events to POST /api/v1/events with a project key. Each project has a timeline of tool calls, decisions, messages, errors, and spans, with the payload you attached.
02
A Monday email, also in the dashboard, for the trailing 7 days: event counts, top tools, recent errors, and anomalies. It goes out around 14:00 UTC. You can turn it off.
03
A daily check flags an error-rate spike, a volume spike, a volume drop, or an agent that went silent. Thresholds are per project. There is no dollar ledger and no risk label. Those show up only as the events you chose to send.
Every plan includes the timeline, the digest, and the alerts. Free is $0 and includes 50,000 events a month. Pro is $39 a month.
Create an account, make a project, and send the first run.
If you are choosing a tracing platform first, read Langfuse vs LangSmith. The production steps are on how to monitor AI agents, and the wider tool list is on AI agent observability tools.
Agent monitoring is the record of what an agent did after it ran: which tools it called, which decisions it took, which errors it hit, and whether that pattern changed. A prompt log does not show a tool loop or an agent that stopped.
Monitor the action timeline, the error rate, event volume, silence, and any tool call you treat as risky. Volume is the closest signal to a cost spike. A risky action shows up only if you record that tool call. AgentTracer does not assign a risk score and does not price tokens.
Four kinds: an error-rate spike, a volume spike, a volume drop, and an agent that went silent after being active. The default check compares the latest window with the earlier baseline, and each project can change those thresholds. It does not ship a separate detector for error loops, dollar cost, or risky tools. A weekly digest email goes out on Monday around 14:00 UTC.
POST /api/v1/events with a project API key. Each event has a type, an optional name, a timestamp, and an optional payload. The types the product expects are tool_call, decision, message, error, and span. Up to 100 events can ride in one request.