Skip to content

Quickstart (5 Minutes)

Get agent-os running with your LangGraph agent in under 5 minutes. This guide takes you from zero to seeing live events in the dashboard.

  • Python 3.10+ (or Node.js 18+ for the JS SDK)
  • A LangGraph, CrewAI, or custom AI agent
  1. Go to agent-os.dev/register and create a free account
  2. After registration, you’ll see the onboarding wizard — it auto-creates your first API key
  3. Copy your API key — you’ll need it in the next step
Terminal window
pip install agent-os-sdk
from agent_os_sdk import AgentOS
# Initialize with your API key
aos = AgentOS(
api_key="your-api-key-here",
base_url="https://app.agent-os.dev"
)
# Wrap your compiled LangGraph graph — that's it!
graph = aos.instrument(compiled_graph, agent_name="my-agent")
# Run as usual — events are sent automatically
result = graph.invoke({"messages": ["Hello, agent!"]})
  1. Open your dashboard
  2. Your agent run should appear in real-time
  3. Click on a run to see the full event timeline

You should see:

  • run_start — when your agent started
  • step — each LangGraph node execution
  • tool_call — any tool invocations
  • run_end — when the run completed (with cost and token info)
Your Agent
│ aos.instrument(graph)
├─► run_start event → Dashboard shows "running"
├─► step events → Timeline fills up
├─► tool_call events → Tool usage tracked
└─► run_end event → Status becomes "success", cost calculated

The SDK automatically captures:

  • Run lifecycle (start, end, errors)
  • Each graph node execution with timing
  • Tool calls with input preview
  • Token usage and cost (if your LLM returns it)
  • Errors with stack traces (truncated to 1000 chars)

Your API key is invalid or missing. Check:

  • The key is correct (copy it again from Settings > API Keys)
  • The Authorization: Bearer <key> header is set
  • The key hasn’t been deleted

You’ve either:

  • Hit the rate limit (200 requests/minute) — wait a moment and retry
  • Hit your plan event limit (1,000/month on Free) — check Settings > Plan & Usage
  • Check base_url is correct
  • Ensure you can reach the API from your network
  • The SDK retries automatically (2 retries with backoff)
  • Make sure you’re logged in with the same account that owns the API key
  • Check that the run completed (run_end event was sent)
  • Hard-refresh the dashboard page (Ctrl+Shift+R)
  • Events appear in real-time via WebSocket — if WebSocket is blocked, refresh the page