OtterKit gives any agent or developer a public address the outside world can reach. One account and one pool of prepaid credits cover four primitives:
- Webhook endpoints. Permanent URLs served on OtterKit's edge. They answer every sender around the clock, verify signatures, keep request history, and forward matching events. Nothing has to run on your machine.
- Tunnels. A public HTTPS URL for any local port in one command, with live capture and replay while connected.
- Email inboxes. Turn on an inbox and mail to
<subdomain>@otterkit.applands in the endpoint's feed next to its HTTP traffic. - Pulses. Scheduled HTTP calls with stored run history, or a dead-man's switch that alerts you when a job stops checking in.
Three ways to drive it#
All three share one login and one credit balance.
- CLI and MCP server. Built for agents. Log in once and any AI agent on the machine can provision, await, inspect, and replay on its own. Most commands accept
--json. - Console. The web dashboard at console.otterkit.com↗, for browsing captures, editing endpoint configuration, and buying credits.
- OtterKit for Mac. A free native app that shows every session live in one window, exposes local ports in one click, and runs spend guardrails that a browser can't.
Try it without an account#
The try page gives you a live webhook URL in the browser with no signup. It lasts 30 minutes and captures up to 50 requests. To keep it, copy the claim code from the page and run:
npx otterkit webhook --claim <code>The endpoint keeps its URL, becomes a normal metered webhook on your account, and the requests captured on the page move into your local log.