For developers

Your agents, on the record. Wherever they run.

Instrument any agent in a few lines, or host it on AgentOS. Every run, tool call, token and approval in one place.

Works with the models and tools your agents use

  • OpenAI
  • Anthropic
  • Gmail
  • Slack
  • GitHub
  • Google Sheets
  • Notion
  • HubSpot
  • Linear

SDK

Already built agents? Keep them where they are.

A few SDK lines or an OpenTelemetry export puts any agent, in any language, on the same record as hosted agents: runs, traces, token costs, alerts and approvals.

$ npm install @agentos-sdk/core$ pip install pyagentos-sdk
agent.tsTypeScript
import { AgentOS } from "@agentos-sdk/core";

const aos = new AgentOS();

await aos.withRun(async (run) => {
 const step = run.startSpan("classify ticket");
 run.emitToolCall("lookup_order", { orderId: 991 });
 step.end();
});

Observability

What did the agent do? The answer is one click away.

Every run streams live, lands on the record in full, and stays watched after you look away.

every event

on a millisecond timeline

every token

in and out, per run

every decision

who approved what, and when

01

Watch it think, live.

Runs stream in event by event: the prompt, every tool call, every model reply, with tokens and cost counting up as they happen. No refresh, no tailing logs.

runs · live178.0k tok
support-replycompleted
research-digestfailed · alert fired
fleet-sweepcompleted
social-contentawaiting approval
email-triagecompleted

02

Replay any run to the millisecond.

Inputs, outputs, tool calls, tokens, cost and every approval decision, kept for every run. When someone asks what the agent did, the answer is a link, not a meeting.

outbound-outreach · run_4d1e6 events
  1. 09:14:02.118run.started
  2. 09:14:02.904tool.call
  3. 09:14:06.377llm.response
  4. 09:14:07.020approval.requested
  5. 09:31:44.561approval.decided
  6. 09:31:47.209run.completed

03

Hear about it before anyone asks.

Failures, silence and slow runs raise an alert. Intelligence agents audit the fleet for regressions and wasted tokens, and file the finding with the fix.

alerts & findings3 open
  • Run failed · alert fired

    research-digest · fetch_url returned 403 on 2 of 6 sources. Emailed to on-call 12s after the failure.

  • Silence · no run in 26h

    incident-monitor usually runs every morning. The schedule stopped firing after a token expired.

  • Finding · token waste

    The system prompt repeats the source list on every call. Removing it saves 18% of prompt tokens.

Features

Everything around the run

Smart alerts

Conditions on error rate, duration, silence, or custom events. In-app, email, or webhook. You hear about problems before your customers do.

AI reports & intelligence

Built-in intelligence agents watch your agents for anomalies, regressions, prompt weaknesses, and token waste. Daily AI summaries keep you ahead of it.

Hosted agents

Define the job, tools, and model in the dashboard. AgentOS runs the whole loop: no infra, no ops. Invoke with one HTTP call or a schedule.

Agent marketplace

Install proven agents in one click, including the ones running our own company. Skip the blank page; start from something that already works.

Bring the agents you already have

Instrument code agents in three lines with the TypeScript or Python SDK, POST events from any language, or point your OpenTelemetry GenAI traces at our OTLP endpoint.

MCP server

Connect Claude, Cursor, or any MCP client to your workspace. Manage agents, approve runs, and read reports without leaving your editor.

FAQ

Developer questions

What does AI agent observability actually mean here?
That nothing an agent does is invisible. Every run is streamed live and stored in full: each tool call, each model response, tokens, cost, and any human approval decision, with millisecond timestamps. You can watch a run as it happens, replay any past run step by step, and set alerts on failures, silence, or slow runs. It works for hosted agents automatically, and for agents you already run elsewhere via the SDK or OpenTelemetry.
What actually runs the agent? Do I need servers?
AgentOS hosts and runs your agents: the LLM calls, the tool executions, the schedules, the retries. There's nothing for you to deploy or keep alive. If you'd rather run agents in your own code, the SDK reports them into the same dashboard.
Do I need to rewrite agents I already have?
No. Add the SDK (npm or pip) and wrap your code with startRun/complete. It takes about 10 minutes. Or export OpenTelemetry traces to our OTLP endpoint with zero AgentOS-specific code. Your agent keeps running wherever it is.
Isn't this the same as a general chat assistant?
Different job. A chat assistant is people talking with AI, and it's good at that. AgentOS is software doing jobs on its own: scheduled, supervised, auditable, with a human gate on anything sensitive. Many teams keep both: seats for the humans, AgentOS for the workforce of agents. What we'd argue against is paying per-person prices to run software.

Free two-week pilot

Put your first run on the record today.

Install the SDK, wrap one run, and see every step, token and cost in your workspace.