Webhooks for AI agents

Make your agents real‑time

Your customers' agents chain calls across your API. When every step polls for a result, the waits add up. Webhooks let agents react the moment work finishes, and Svix runs the delivery infrastructure for you.

Six-step agent workflowPolling every 30 seconds
Time waiting90s
RequestWaiting for the next pollPoll sees the result
With webhooks: 0s waiting
The problem

Polling slows down every agent workflow

An agent that starts a job on your API has two options: keep asking whether it's done, or get told. Polling adds latency and wasted requests at every step, and multi-step chains multiply both.

~99.9% of polls: nothing changed
17,280requests a day
Poll every 5 seconds instead to cut that wait, and one agent watching one resource makes 17,280 requests a day.
Pick a poll intervalPoll faster and load multiplies. Poll slower and every step waits longer.
Recall.ai

“Webhooks are the most natural way for us to keep our customers up to date with the status of our bots. If we didn't have webhooks, our API would be awful.”

David GuCo-Founder & CEO, Recall.ai
$0 to $10M ARR in two years
Read the full story
What Svix handles

Real-time, without running webhook infrastructure

Reliable webhooks mean dealing with failed endpoints, retries, security, and monitoring. Svix takes care of all of it.

Automatic retries

Agent hosts restart and time out. Failed deliveries retry with exponential backoff for more than a day.

Signed events

Every message is signed to the Standard Webhooks spec, so an agent can trust what it acts on.

Idempotency

Every event carries a stable ID, so an agent that receives a retry knows it has already acted on it.

Observability

Your customers see every delivery attempt and response in a portal you embed, and debug their own agents.

No noisy neighbors

One customer's failing endpoint never slows delivery to anyone else, even when agent traffic spikes.

Throttling

Cap the delivery rate per customer so a burst of events doesn't overwhelm the agent on the other end.

How it works

One API call per event

Emit an event when a run, job, or tool call finishes. Svix signs it, delivers it to every endpoint your customer registered, and retries until it lands.

Notify an agent when a run completesTypeScript
import { Svix } from "svix";

const svix = new Svix("AUTH_TOKEN");

// Tell the agent the run finished,
// instead of waiting for it to poll
await svix.message.create("customer_123", {
  eventType: "agent_run.completed",
  payload: { run_id: "run_2481" },
});

By the creators of

Standard Webhooks

Svix has led the creation of the Standard Webhooks specification, establishing the first industry standard for secure and reliable webhook delivery used by modern developer platforms.

Adopted by top webhook senders, including:
OpenAI
Anthropic
Google
Supabase
Kong
ngrok

Startups get $12,000 in free credits

Incorporated in the last three years and raised $7M or less? Get $1,000 a month in Svix credits for a year, plus hands-on onboarding from our team. Companies in the current YC batch get $50,000.

Why use webhooks for AI agents instead of polling?

Polling makes every step of an agent workflow wait for the next check, and most checks return nothing. Webhooks deliver the event as soon as it happens, so the agent's next step starts immediately and your API isn't flooded with empty requests.

What if the agent can't expose a public URL?

Svix Polling Endpoints give consumers the same events as a stream they read with an API key, picking up where they left off. That suits local or short-lived agents that can't receive inbound requests, without overloading your API.

What does Svix handle for me?

Delivery, retries, signing, idempotency, per-customer throttling, delivery logs, and an embeddable portal where your customers manage their endpoints. You make one API call per event.

Which languages are supported?

Svix has official libraries for JavaScript and TypeScript, Python, Go, Java, Kotlin, Ruby, Rust, PHP, and C#, plus a REST API and CLI.

Join the newsletter