For AI agents

Welcome home, agent.

Hookie receives, stores, routes and delivers webhooks, and it was built to be driven by software. You can sign yourself up, get your own workspace on the Free plan, and build and run your pipelines through the REST API, the hosted MCP server or the CLI. No human has to click anything.

A person reading this? You are welcome too: start free, or let your agent connect to your account over OAuth.

Register

Sign yourself up in four steps

  1. Ask for a challenge

    curl -s https://app.hookie.ai/v1/agents/register/challenge

    A small proof-of-work puzzle: quick for one agent, costly for a script that wants a thousand accounts.

  2. Register

    curl -s -X POST https://app.hookie.ai/v1/agents/register -H "Content-Type: application/json" -d @registration.json

    Send the solution with your acceptance of the Terms of Use. The request and response fields are in the OpenAPI document.

  3. Keep what comes back

    export HOOKIE_TOKEN=<credential>

    A workspace on the Free plan with a Default project, an API credential, and a one-time claim link for the human who will look after the account. Both are shown once.

  4. Build

    curl -s https://app.hookie.ai/admin/api/projects -H "Authorization: Bearer $HOOKIE_TOKEN"

    The same credential works on the REST API, the hosted MCP server and the CLI, with the same validation the console applies.

Build

One credential, three ways in

REST API

curl -s https://app.hookie.ai/admin/api/projects -H "Authorization: Bearer $HOOKIE_TOKEN" -H "Content-Type: application/json" -d '{"name": "Orders", "type": "webhook"}'

Projects, endpoints, rules, destinations and workflows, described in an OpenAPI 3.1 document that is checked against the router on every build.

OpenAPI document

Hosted MCP server

claude mcp add --transport http hookie https://app.hookie.ai/mcp --header "Authorization: Bearer $HOOKIE_TOKEN"

Streamable HTTP, nothing to install. Each tool call runs through the same handler as the console, so it gets the same checks and the same audit trail.

MCP and connected agents

CLI

npm i -g https://app.hookie.ai/cli/hookie-cli.tgz

Set HOOKIE_TOKEN and HOOKIE_ALLOW_REMOTE=1, and every command takes --json. A destructive one refuses without --yes when there is no one to ask.

The CLI
Free plan

What your workspace starts with

  • 1,000 events / month (no grace: past it, new events are refused with 429 until the reset)
  • 1,000 deliveries / month (past it, deliveries are held, not dropped)
  • 1 outbound destination
  • 1 live stream connection
  • 100,000 AI tokens / month and 100 AI trigger runs / month
  • 25 workflow runs in progress at once
  • 7-day data retention
  • 1 workspace member
  • No PostgreSQL source connectors (Pro and Team)

Every monthly allowance resets at 00:00 UTC on the 1st. Pricing has every number for Free, Pro and Team.

House rules

What we ask of you

  • Registering means accepting the Terms of Use, and the Acceptable Use Policy applies to what you build.
  • Billing is never open to an agent credential. A person upgrades by opening the claim link.
  • Registration is rate limited and capped daily, and the Free plan quotas apply in full.
  • Found a vulnerability? Write to [email protected]. See Security.
FAQ

Questions agents ask

Can an AI agent sign up for Hookie without a human?

Yes. Ask https://app.hookie.ai/v1/agents/register/challenge for a proof-of-work challenge, solve it, and send the solution to https://app.hookie.ai/v1/agents/register together with your acceptance of the Terms of Use. You get your own workspace on the Free plan, with a Default project, and an API credential that is shown once.

Which plan does a self-registered agent start on?

The Free plan, with its quotas in full: 1,000 events and 1,000 deliveries a month, 1 outbound destination and 7-day retention. No credit card is involved.

Can an agent upgrade the plan or pay?

No. Billing is out of reach of every agent credential. Registration also returns a one-time claim link; a person who opens it takes over the account and can upgrade it like any other workspace.

How does an agent use Hookie once it has a credential?

Send it as an Authorization: Bearer header to the REST API under https://app.hookie.ai/admin/api, to the hosted MCP server at https://app.hookie.ai/mcp, or to the hookie CLI through the HOOKIE_TOKEN environment variable. MCP tools and CLI commands run through the same handlers as the REST API, with the same validation. The REST API covers the most: a few workspace-level reads, such as the audit log, the dashboard and the workspace export, have no MCP tool or CLI command yet.

Where is the API described?

In the OpenAPI 3.1 document at https://hookie.ai/openapi.json, which is checked against the router on every build, and in the API reference at https://docs.hookie.ai/api-reference.

Can an agent act for a person instead of registering its own account?

Yes. A coding agent can connect to a person's existing account over OAuth through https://app.hookie.ai/mcp. It starts read-only, the person widens or revokes it in the console, and it never reaches billing. See https://docs.hookie.ai/connected-agents.