> ## Documentation Index > Fetch the complete documentation index at: https://docs.hookie.ai/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Capture any HTTP event, route it into structured datasets, run it through a workflow, and deliver it signed — on Cloudflare's edge. Hookie is a webhook platform: it gives you a URL to receive events, somewhere structured to keep them, logic to act on them, and a signed, retrying delivery out the other side. Everything runs on Cloudflare Workers, D1, and Durable Objects. > [card] [Quickstart](https://docs.hookie.ai/quickstart.md) > > Create a project, send a test event, see the record, and watch a signed delivery arrive. > [card] [Workflows & AI agents](https://docs.hookie.ai/workflows.md) > > Multi-step, event-driven pipelines with branching, AI steps, and reusable agents. > [card] [API reference](https://docs.hookie.ai/api-reference.md) > > Every ingest, admin, and streaming endpoint, with an interactive playground. > [card] [Connected agents](https://docs.hookie.ai/connected-agents.md) > > Point Claude Code, Cursor, or any MCP client at your workspace over OAuth. > [card] [Agent self-registration](https://docs.hookie.ai/agent-self-registration.md) > > Let an AI agent create its own Free-plan account, with no person involved. ## How an event moves through Hookie **1. It arrives** Post to an endpoint's URL, where the high-entropy slug in `app.hookie.ai/{workspace}/{project}/{webhook}` is the credential, or to `/v1/ingest/{key}` with an ingest key. JSON, form posts, and multipart all work, so an HTML `
` can point straight at an endpoint with no JavaScript and no backend of your own. Before anything is stored, the request passes the endpoint's IP allowlist, its rate limit, a duplicate check (an `Idempotency-Key`, or the delivery id your provider already sends), and your plan quota. Refused requests are logged in the endpoint's Activity, and never counted. **2. It's captured, then routed** The raw body is stored as a **submission** exactly as it arrived, before anything reshapes it, so "no rule matched" is always distinguishable from "the event never arrived." Addressed requests store the payload whole into the dataset the URL names. A keyed request with no dataset in the path is the one shape that consults **rules**: each enabled rule tests its conditions against the payload and, where they hold, maps fields out into a **record**. Rules are not first-match: one event can land in several datasets at once. An event no rule matches is stored whole in the key's default dataset rather than dropped. **3. It fans out** A new record triggers every matching **destination** (an outbound webhook, signed HMAC-SHA256, retried with backoff), pushes onto the **live stream** for anyone tailing it, and starts any **workflow** whose trigger it satisfies. **4. It gets acted on** A workflow runs steps in order: call a model, branch on the result, write to a dataset, emit a further event. Workflows also start on a schedule or from a WebSocket condition, not only from an inbound event. ## What's in the box > [card] [Signed delivery](https://docs.hookie.ai/signatures.md) > > Outbound webhooks carry an HMAC-SHA256 signature and a timestamp. Verify them in a few lines, in any language. > [card] [Live streaming](https://docs.hookie.ai/streaming.md) > > Tail events in real time over SSE or WebSocket, with resume after a disconnect. > [card] [Customer portal](https://docs.hookie.ai/customer-portal.md) > > Let your own customers manage their webhook destinations and inspect their deliveries, without a support ticket. > [card] [Observability & search](https://docs.hookie.ai/quickstart.md#trace-an-event-later) > > Search submissions, records, and deliveries, and follow any ID along the whole chain it belongs to. > [!NOTE] > > Every resource (datasets, rules, endpoints, destinations, workflows) is scoped to a **project**, and every workspace starts with a Default project. If you are just trying things out, you can ignore projects entirely and use that one. [Projects](https://docs.hookie.ai/projects.md) and the other **Concepts** pages explain how the pieces fit, and the [Glossary](https://docs.hookie.ai/glossary.md) defines every term. ## Finding your way around the console **Home** is the workspace at a glance. It charts events received, deliveries sent and AI runs over the last 24 hours, 7 days or 30 days, each with its change on the period before. It also shows this month's usage against your plan, and a **Needs attention** list of anything that wants you: a failing or automatically disabled destination, or a limit you are close to. Its search box reaches any project, page or setting, and **Recently opened** lists the pages you visited last. The side navigation groups an open project's pages under **Build** (endpoints, ingest keys, datasets, rules, workflows), **Deliver** (connections, deliveries) and **Observe** (observability, errors). Press / or ⌘K (Ctrl+K on Windows and Linux) to filter it as you type. ## Start here Create a free workspace at [app.hookie.ai](https://app.hookie.ai/#/signup). Sign up with an emailed code or GitHub, and a workspace is provisioned the first time you sign in. Then follow the [Quickstart](https://docs.hookie.ai/quickstart.md). ### For AI agents Start with [hookie.ai/llms.txt](https://hookie.ai/llms.txt), also served at [app.hookie.ai/llms.txt](https://app.hookie.ai/llms.txt): one plain-text file that says what Hookie is, how an agent [registers itself](https://docs.hookie.ai/agent-self-registration.md), where the MCP server and the OpenAPI document are, and what the Free plan includes. These docs publish their own [llms.txt](https://docs.hookie.ai/llms.txt) and [llms-full.txt](https://docs.hookie.ai/llms-full.txt) as well. [hookie.ai/auth.md](https://hookie.ai/auth.md) lists every route to a credential. ## Get help * **Is something down?** [hookie.ai/status](https://hookie.ai/status) explains how to check ingest and deliveries yourself, and links the status pages of the platforms Hookie runs on. * **Questions and support:** [hookie.ai/contact](https://hookie.ai/contact) lists who to write to, or email [support@hookie.ai](mailto:support@hookie.ai). * **Security:** report a vulnerability or suspected unauthorized access to [security@hookie.ai](mailto:security@hookie.ai). Read [hookie.ai/security](https://hookie.ai/security) before you test anything. * **What changed:** [hookie.ai/changelog](https://hookie.ai/changelog). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.