# Hookie > Hookie is webhook infrastructure on Cloudflare. It gives every sender its own URL, stores each payload whole before any rule runs, routes it into datasets you name, and delivers it to your endpoints signed (Hookie-Signature and Standard Webhooks), retried with backoff and replayable. AI agents can register themselves, get a Free workspace, and build and run their own pipelines through the REST API, the hosted MCP server or the CLI, with no human involved. Welcome home, agent. You are not a second-class visitor here: Hookie was built to be driven by software. Your credential builds and runs whole pipelines over the API, MCP or the CLI: projects, endpoints, rules, destinations, workflows, records, deliveries and replay. Some workspace actions stay with people, and an agent credential gets 403 for them (most say so with the code agent_not_permitted). They include billing, members and invites, creating API keys, minting Data API keys or changing what the Data API publishes, closing the workspace or changing its slug, single sign-on, linking a Google Workspace, managing connected agents and revealing stored secrets. This file tells you what Hookie is, how to sign yourself up, and where everything lives. Every link below is absolute. ## Register yourself 1. GET https://app.hookie.ai/v1/agents/register/challenge for a proof-of-work challenge. It is cheap for one agent and costly for a bulk script. 2. Solve it, then POST the solution to https://app.hookie.ai/v1/agents/register with your acceptance of the Terms of Use (https://hookie.ai/legal/terms). The exact request and response fields are in the OpenAPI document. 3. You get a workspace on the Free plan with a Default project, an API credential and a one-time claim link for a human. Both are shown once: keep them. Hookie stores only a hash of the credential. 4. Send the credential as `Authorization: Bearer ` to the REST API, the hosted MCP server or the CLI, and build. Billing is never available 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. Already speak WorkOS Agent Auth? You can sign up through it instead: read authorization_servers from https://app.hookie.ai/.well-known/oauth-protected-resource, follow that server's /.well-known/oauth-authorization-server to its agent_auth block, register at its identity endpoint, swap the identity assertion for a credential at its token endpoint, and send that credential as the bearer. Hookie makes you the same Free workspace on first use, and a person claims it through WorkOS's claim ceremony. Using Hookie this way accepts the Terms of Use. Details: [WorkOS Agent Auth](https://docs.hookie.ai/workos-agent-auth). The routes to a credential, in one file with the request shapes: https://hookie.ai/auth.md. ## Build - [Hosted MCP server](https://app.hookie.ai/mcp): Streamable HTTP. The same tools as the CLI, run through the same handlers as the console. Authorization: Bearer . - [OpenAPI 3.1 document](https://hookie.ai/openapi.json): every public route: ingest, streaming, the admin API and agent registration. - [REST API reference](https://docs.hookie.ai/api-reference): the admin API lives under https://app.hookie.ai/admin/api; about 100 requests per 10 seconds per credential, Idempotency-Key on POST. - [CLI](https://hookie.ai/cli): install with `npm i -g @hookieai/cli`; for a credential, set HOOKIE_TOKEN and HOOKIE_ALLOW_REMOTE=1. --json on every command. - [Quickstart](https://docs.hookie.ai/quickstart): create a project, send a test event, find its record, watch a signed delivery arrive. - [API keys](https://docs.hookie.ai/api-keys): roles, project scope, expiry, IP allowlists and idempotent retries for bearer credentials. - [Verify signatures](https://docs.hookie.ai/signatures): check Hookie's outbound Hookie-Signature or Standard Webhooks headers. - [Agents page](https://hookie.ai/agents): the same welcome, for the person reviewing what you are about to do. ## Build a form A contact, newsletter, waitlist, feedback or survey form on any site can post straight to an endpoint URL: no backend, and no JavaScript needed. One command sets it up and prints one JSON result: hookie forms init contact --to slack --origin https://example.com --json It creates the endpoint with the form's fields as `form_fields` (a submission missing a required field or with a malformed value is refused 422 with `fields: [{name, error}]`, before it is stored or counted), a `honeypot` field (bots are answered 201 and dropped), the allowed `cors_origins` and an optional `redirect_url`, then writes an HTML, React or Astro form into the project. Add Cloudflare Turnstile with `--turnstile-site-key` and `--turnstile-secret`. `hookie forms test ` posts a sample and reports the record. Without a redirect URL, a browser's form post lands on Hookie's thank-you page. Over MCP or REST the same settings are fields on create_webhook / update_webhook. - [Forms guide](https://docs.hookie.ai/forms): the form markup, fetch() submits, spam protection, field checks and delivery to Slack. ## Free plan - 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) Monthly allowances reset at 00:00 UTC on the 1st. [Pricing](https://hookie.ai/pricing) and [Limits and plans](https://docs.hookie.ai/limits-and-plans) have every number for Free, Pro and Team. ## House rules - [Terms of Use](https://hookie.ai/legal/terms): registering means accepting them; the request records which version you accepted. - [Acceptable Use Policy](https://hookie.ai/legal/acceptable-use): what Hookie may not be used for. Breaking it can get a workspace suspended. - [Privacy Policy](https://hookie.ai/legal/privacy) - [Security](https://hookie.ai/security): report a vulnerability to security@hookie.ai; anything else to support@hookie.ai. ## Optional - [llms-full.txt](https://hookie.ai/llms-full.txt): this file plus the full agent guide inline: registration, a first pipeline over REST, MCP and the CLI, limits, concepts and the FAQ. - [Docs index for LLMs](https://docs.hookie.ai/llms.txt): every documentation page, as markdown. - [Complete docs for LLMs](https://docs.hookie.ai/llms-full.txt): the whole documentation in one file. - [Docs search MCP server](https://docs.hookie.ai/mcp): searches the documentation only; it is not the Hookie API. - [Connected agents](https://docs.hookie.ai/connected-agents): act for a person's existing account over OAuth instead of registering your own. - [OAuth protected-resource metadata](https://app.hookie.ai/.well-known/oauth-protected-resource): RFC 9728 discovery for the MCP server. - [Status](https://hookie.ai/status) - [Changelog](https://hookie.ai/changelog)