AgentPing docs

One ingest pipeline, one dashboard, three answers about your production agents: what they cost, whether they're running, whether their answers are still good.

How it works

<title id="ap-arch-title">AgentPing architecture overview</title> Your agents send runs, events, and heartbeats over HTTP to the AgentPing ingest endpoint, which scores, routes, and surfaces them as Spend, Pulse, and Verify signals via the dashboard, email, webhook, and API. 001 · your agents Python TypeScript Go Laravel curl · cron n8n · GitHub Actions Zapier · any HTTP run event heartbeat 002 · AgentPing ingest runs · events heartbeats · ping workers cost · check judge · alert score route surface 003 · operators SPEND what it costs PULSE is it running VERIFY is it still good dashboard · email webhook · API

A run is one invocation of an agent. The SDK (or any HTTP caller) opens it, appends events as the agent works, closes it with a terminal status. Heartbeats are the shortcut: one HTTP call, one finished run.

Next steps