# Hook0 > Hook0 is a webhook sending service from FGRibreau SARL in France. An application posts events to a REST API and Hook0 signs, retries and logs deliveries to subscriber endpoints. It runs as an EU-hosted cloud or self-hosted under SSPL-1.0. - Canonical: https://www.anchorterminal.com/tools/hook0 - Markdown: https://www.anchorterminal.com/tools/hook0.md (~7,850 tokens) - Slim: https://www.anchorterminal.com/tools/hook0.min.md (~1,830 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/hook0.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade B · 64.6/100 · rank #313 of 842 · #5 in Event delivery & webhooks · not agent-ready · confidence medium** ## Assessment Hook0 Cloud sends signed webhooks from one REST call, with a public OpenAPI document, RFC 7807 errors and service tokens that can be narrowed offline to one application, an expiry or read-only actions. Six security advisories were published between August and September 2026, one rated High. Signup needs a browser check, and no uptime commitment exists below Enterprise. ## Facts | Field | Value | | --- | --- | | Vendor | FGRibreau SARL (https://www.hook0.com) | | Kind | HTTP API | | Category | Event delivery & webhooks (https://www.anchorterminal.com/categories/webhooks) | | Transport | HTTP, stdio | | Auth | API key · Every call takes `Authorization: Bearer ` at https://app.hook0.com/api/v1. A person signs up in a browser, passes a Cloudflare Turnstile check and verifies an email address, then creates a service token in the dashboard. Service tokens are Biscuit tokens scoped to one organisation, and the holder can narrow one offline to a single application, an expiry date or an allowlist of actions. Each application also has secrets that work as Bearer tokens with full control of that application. No OAuth for API clients. | | Pricing | Freemium (Freemium) · Free Developer plan with no card, 100 events a day, one application and 7 days of retention, and a 429 once the quota is used. Startup is €59 a month for 30,000 events a day, then €0.003 an event. Pro is €190 a month for 100,000 events a day, then €0.0001 an event. Prices exclude VAT and are published in euros only. Subscriptions and retries aren't counted. Self-hosting is free, and a managed on-premise instance is €500 a month plus €1,000 setup (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the documentation index, the OpenAPI document, the repository or the pricing page (checked 2026-10-08). | | Licence | SSPL-1.0 for the server (source available, not an OSI licence). The SDKs and the `hook0-mcp` server are MIT per crates.io and npm. Hook0 Cloud is a hosted service under Hook0's terms of service | | Tools exposed | 23 | | Packages | npm: `hook0-client`; pypi: `hook0-client`; cargo: `hook0-mcp` | | Source | https://github.com/hook0/hook0 | | Docs | https://documentation.hook0.com/ | | llms.txt | https://documentation.hook0.com/llms.txt | | Last release | 2026-09-21 | | GitHub stars | 1,494 (as of 2026-10-08) | | npm downloads / week | 507 | | PyPI downloads / week | 11 | | API | REST at https://app.hook0.com/api/v1, version 1.0.2, OpenAPI 3.0 with 56 operations on 38 paths. 36 are tagged for the SDKs and 23 for the MCP server | | MCP server | `hook0-mcp` 3.0.0 on crates.io, stdio only, 23 tools named `.`, eight `hook0://` resources and three prompts. It makes one attempt per call and no retries | | Credentials | Biscuit service tokens per organisation, narrowed offline by application, expiry or action list. Application secrets with full control of one application. Bearer header only | | Rate limits | 10 requests a second per token, 100 per IP and 1,000 overall, per the API introduction. Daily event quotas of 100, 30,000 and 100,000 by plan | | Errors | RFC 7807 problems with `type`, `id`, `title`, `detail` and `status`. 46 codes in the reference. 429 carries `Retry-After` | | Idempotency | Optional client `event_id` (UUID). A repeat is rejected with `EventAlreadyIngested` (409). `POST /api/v1/events/{event_id}/replay` resends an event to matching subscriptions | | Retries | From 3 seconds to 10 hours between attempts, 24 retries by default, with slower delivery to subscriptions whose endpoints are failing | | Signatures | HMAC-SHA256 in `X-Hook0-Signature` with a timestamp, the signed header names and a `v1` signature, keyed by the subscription's secret | | SDKs | JavaScript and TypeScript, Rust, Python, Go, Ruby, PHP, C#, Java, Kotlin, Lua and Zig, generated from the API snapshot. `hook0-client` 2.0.3 on npm, PyPI and crates.io (28 August 2026), MIT | | CLI | `hook0`, installed with `cargo install --git https://gitlab.com/hook0/hook0.git hook0-cli`. It sends and replays events and tunnels webhooks to localhost with `hook0 listen` | | Retention | Event data for 7 days on Developer, 14 on Startup and 30 on Pro. Account data for 30 days after termination | | Hosting | Clever Cloud in France, with delivery workers on Clever Cloud and Scaleway and Cloudflare for DNS and DDoS protection | | Status | status.hook0.com on Better Stack, twelve components with 90 days of daily history, also served as JSON at `/index.json` | | Self-hosting | Docker Compose, Kubernetes or bare metal from the same repository, SSPL-1.0. Development happens on GitLab and GitHub is a mirror | | Capabilities | events.webhooks-send | | Tags | hosted, self-hosted, source-available, webhooks, api-key, openapi, llms-txt, mcp, free-tier, no-card, status-page, eu-hosted, typescript, python, rust, go | | JSON | https://www.anchorterminal.com/api/v1/tools/hook0.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 70 | 14.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 79 | 12.8 | | Agent ergonomics | 13% | 16.2 | 65 | 10.6 | | Security & auth | 14% | 17.5 | 64 | 11.2 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 87 | 7.6 | | Transparency & trust (editorial 76, provenance 91) | 7% | 8.8 | 84 | 7.3 | | Negative events | up to −15 | up to −15 | 2026-08-11. Server-side request forgery in the delivery worker, rated High by the vendor. An IPv6 transition address passed the filter on forbidden targets, so a tenant could make the worker reach internal addresses. Fixed in commit 3b27e932 and published with the reporter credited, so the deduction is reduced to 3 (https://documentation.hook0.com/resources/security-advisories). 2026-08-24. A password reset link stayed usable after it had reset a password, rated Medium, which allowed account takeover by anyone holding a spent link. Fixed in commit 80fae0de and published, so the deduction is 1 (https://documentation.hook0.com/resources/security-advisories). | -4 | | **Total** | | | | **64.6 → B** | ### Why each score - Reliability 70: Graded as a hosted service, Hook0 Cloud. status.hook0.com on Better Stack lists twelve components with 90 days of daily history (20). Two incident reports fall in the 90 days to 8 October 2026. On 27 August the API and delivery were unavailable for about 18 minutes, and on 22 September an object storage outage at the host stopped ingestion and delivery, with the page recording 12 minutes on the API and 73 minutes on the delivery workers. The daily history also records about 18 minutes of API downtime on 13 July and 15 minutes on 8 October. We read the 22 September delivery outage as one major outage (10). Limits of 10 requests a second per token, 100 per IP and 1,000 overall are documented, with daily event quotas by plan (15). A 429 carries `Retry-After` and its problem text says the request is safe to resend, and a client `event_id` makes ingestion retries safe (15). The terms state that no uptime commitment exists outside a signed Enterprise agreement (0). The API is at version 1.0.2 and generally available (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 79: OpenAPI 3.0 document served without a login at app.hook0.com/api/v1/swagger.json, 56 operations on 38 paths (25). llms.txt on both the site and the documentation, listing every documentation page (10). Every operation has a summary and a description that states its purpose and often when to use it, with little on when not to (14). Required fields, UUID and date-time formats and length limits are typed, but the snapshot holds nine enums, `payload_content_type` lists its valid values only in prose and `labels` is a free map by design (10). Ten error statuses on every operation and a reference of 46 error codes with sample bodies, against two examples in the spec. The API introduction page shows a different error body and `limit`, `offset` and `sort` parameters that the spec doesn't have (10). The path carries `/api/v1`, each component has a changelog in the repository and tagged releases on GitLab, and the documentation's changelog page only links to GitHub Releases (10). - Agent ergonomics 65: `GET /api/v1/events/` returns the 100 most recent events with no size or field parameter. The MCP server has 23 tools, or 13 in read-only mode (12). Only the delivery attempt list is paginated, by cursor through a `Link` header, with filters for event, subscription, date range and event type. Other lists take `application_id` alone (8). Errors are RFC 7807 problems with a stable `id` and a documentation URL per code, though the API introduction page describes another shape (18). A client-supplied `event_id` is rejected on reuse with `EventAlreadyIngested`, the SDKs mint the id before retrying and `POST /api/v1/events/{event_id}/replay` resends an event. The MCP tools carry no read-only or destructive annotations (15). An event needs six fields. Official clients exist for eleven languages (12). - Security & auth 64: Service tokens are Biscuit tokens, revocable from the dashboard or the API, which the holder can narrow offline to one application, an expiry date or an allowlist of actions. Revoking a root token invalidates every token derived from it. Application secrets can't be narrowed and control their whole application. No OAuth for API clients (28). A read-only token is documented with the claim to paste, and `HOOK0_READ_ONLY` hides the MCP server's ten write tools. Deletes need no confirmation (14). Delivery logs return subscriber endpoints' response bodies, which are third-party content, and no guidance for agents reading them was found (5). Every delivery attempt is stored with its response. The security model page shows an audit log record, but no audit log an operator can read was found in the API or the documentation (7). Valid security.txt, a disclosure policy with a discretionary reward for critical findings, a PGP key and advisories published with credits. Hook0 holds no SOC 2 or ISO 27001 certificate of its own and cites its host's (10). - Payments & pricing 40: Graded on Hook0 Cloud. No x402, MPP or L402 (0). Plan prices and per-event overage (€0.003 on Startup, €0.0001 on Pro) are public (20). The Developer plan is free with no card, limited to 100 events a day (20). `POST /api/v1/register/` exists, but the cloud instance requires a Cloudflare Turnstile token and email verification, so a person has to sign up (0). The self-hosted server is free to run. We graded the hosted service. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 87: The newest tagged release is `frontend/v1.2.1` on 21 September 2026, 17 days before this check, and the default branch had commits on 8 October (30). Since 10 July GitLab lists nine component releases, among them `mcp/v3.0.0` on 26 August and five output worker releases in early August, and the SDKs went from 2.0.0 to 2.0.3 between 25 and 28 August (20). GitLab shows eight open issues, the latest updated on 2 October 2026 and five untouched since December 2025. Six security reports were fixed and published between August and September. Support is by email and Discord (15). Clients for eleven languages are generated from the API snapshot, with `hook0-client` 2.0.3 on npm, PyPI and crates.io (15). Dependency update commits landed on 29 September and the repository has GitLab CI, OSV and Trivy configuration. We couldn't read the pipeline results (7). - Transparency & trust 84: The server's source is public under SSPL-1.0, which the terms themselves say the OSI hasn't approved, and the SDKs and MCP server are MIT. The cloud runs the same code (20). A privacy policy updated 9 September 2026, a published DPA and terms that agree on retention, 7, 14 and 30 days of event data by plan and 30 days after termination, with breach notice within 72 hours and a public Article 30 register (28). The terms of sale promise 90 days' notice before the free plan is cut and the terms 30 days for material changes. No deprecation policy for the API was found (8). Sub-processors are listed with countries, and the data plane is on Clever Cloud in France with Cloudflare in front (20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (22 items): https://www.anchorterminal.com/fixes/hook0.md (JSON https://www.anchorterminal.com/fixes/hook0.json) ### What we couldn't check - The lead called Hook0 open source. The server is under SSPL-1.0, which the OSI hasn't approved, and the vendor's terms say so. The SDKs and MCP server are MIT - The lead named a CLI. It isn't on crates.io and installs from the GitLab repository with `cargo install --git` - unchecked: whether the rate limits on Hook0 Cloud match the documented defaults (10 a second per token). We sent no authenticated request - unchecked: the GitLab pipelines API answered 403, so the pass state of CI on the default branch wasn't read - unchecked: whether `hook0-mcp` is in the official MCP registry. We didn't query it, and the repository has no `server.json` - unchecked: GitHub's release list, which the documentation's changelog page points to. The clone carries three tags, all `frontend/`, and GitLab lists 17 releases - Prices are published in euros only, so the listing has no unit prices in dollars - The status page's daily history records 73 minutes of delivery worker downtime on 22 September 2026, while the incident updates report recovery after 12 minutes. We scored the longer figure - No audit log of dashboard or API actions was found, although the security model page shows a sample audit record - First release date not established. The GitLab project dates from 15 November 2020 and the GitHub mirror from 20 July 2021 ### Sources - site index for assistants (llms.txt): (seen 2026-10-08) - documentation index (llms.txt): (seen 2026-10-08) - robots.txt, no Content-Signal line: (seen 2026-10-08) - pricing: (seen 2026-10-08) - pricing and billing, quota behaviour: (seen 2026-10-08) - terms of service: (seen 2026-10-08) - terms of sale: (seen 2026-10-08) - privacy policy: (seen 2026-10-08) - data processing addendum: (seen 2026-10-08) - security and compliance page: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - security advisories: (seen 2026-10-08) - vulnerability disclosure policy: (seen 2026-10-08) - security measures and rate limiters: (seen 2026-10-08) - live OpenAPI document: (seen 2026-10-08) - instance settings (registration, Turnstile): (seen 2026-10-08) - API introduction (rate limits, pagination, error shape): (seen 2026-10-08) - error codes reference: (seen 2026-10-08) - service tokens and attenuation: (seen 2026-10-08) - application secrets: (seen 2026-10-08) - MCP server reference, tool table: (seen 2026-10-08) - MCP setup guide: (seen 2026-10-08) - retry schedule: (seen 2026-10-08) - events and idempotency: (seen 2026-10-08) - support and response times: (seen 2026-10-08) - status page as JSON, incident reports and daily history: (seen 2026-10-08) - repository mirror (documentation, API snapshot, MCP source, changelogs), cloned: (seen 2026-10-08) - GitLab releases: (seen 2026-10-08) - GitLab open issues: (seen 2026-10-08) - crates.io hook0-mcp: (seen 2026-10-08) - npm hook0-client: (seen 2026-10-08) - PyPI hook0-client: (seen 2026-10-08) - RDAP for hook0.com: (seen 2026-10-08) ## Who's behind it (provenance 91/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | FGRibreau SARL | 20/20 | | Domain age | hook0.com, registered 2020-09-02 (6 years) | 11/15 | | Endpoint on the vendor's domain | hook0.com | 15/15 | | Terms of service | read, states 7 of the 7 things a reader expects, and has 2 clauses that cost points | 6/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.hook0.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The terms of service (last updated 27 June 2026) name FGRibreau SARL, a French limited liability company registered at La Roche-sur-Yon under number 850 824 350, with its office at 3 rue de l'Aubepine, 85110 Chantonnay, France. The API answers at app.hook0.com, a hook0.com subdomain, per the OpenAPI document's server entry. www.hook0.com/.well-known/security.txt names security@hook0.com, a disclosure policy and an acknowledgments page, and expires on 6 August 2027. The privacy policy (last updated 9 September 2026) covers the Hook0 service and lists sub-processors with countries. A data processing addendum is published at www.hook0.com/data-processing-addendum. The documentation's changelog page only links to GitHub Releases. Releases are tagged per component on GitLab, where development happens, and each component keeps a CHANGELOG.md. RDAP for hook0.com gives a registration date of 2020-09-02. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.hook0.com/terms), read 2026-10-08, dated 2026-06-27, states 7 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "(g) use automated means to access or scrape the Service except through the official API and in accordance with the Documentation;" - To know. Says the terms or the service can change without notice (costs points). "Hook0 may modify these Terms without prior notice for changes that are purely administrative (such as corrections of typographical errors or updated contact information) or that are required by law." - To know. Says access can be ended without notice or for any reason. "Hook0 may terminate these Terms for any reason upon 30 days' written notice." - Gives the date it was last updated. Last updated 2026-06-27. - Names the governing law or courts. Disputes go to the courts of La Roche. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Gives 15 days of notice before a change. - Also in the text (2026-10-08). After termination Hook0 keeps customer Content for 30 days, during which an export can be requested, and may then delete it permanently. "(c) Hook0 will retain your Content for 30 days after the effective date of termination, during which period you may request an export of your data by contacting [email protected];" - Also in the text (2026-10-08). Each legal entity may hold only one Account unless Hook0 agrees otherwise in writing. "Each legal entity may maintain only one Account unless expressly agreed otherwise by Hook0 in writing." - Also in the text (2026-10-08). The licence over customer Content is limited to processing and storing it as needed to run the Service, and Hook0 states it will not use Content for any other purpose. "By submitting Content through the Service, you grant Hook0 a limited, worldwide license to process and store your Content solely to the extent necessary to provide the Service." **Privacy policy** (https://www.hook0.com/privacy-policy), read 2026-10-08, dated 2026-09-09, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2026-09-09. - Says how long data is kept. Names a period of 13 months. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. Gives an email address, hidden from our reader by the page. - Says where data is transferred or stored. Relies on standard contractual clauses and the Data Privacy Framework. ## Live (updated 2026-10-09 07:58 UTC) - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/hook0.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Public OpenAPI 3.0 document at `/api/v1/swagger.json` with 56 operations, each with a summary, a description and ten error statuses - Service tokens are Biscuit tokens that the holder can narrow offline to one application, an expiry date or a read-only action list - Errors follow RFC 7807 with a stable `id`, and the reference lists 46 codes generated from the API's own `/errors` endpoint - Free Developer plan of 100 events a day with no card, and per-event overage prices published for both paid plans - Retention by plan, sub-processors with countries, a DPA, a GDPR Article 30 register and a transfer impact assessment are all public ## Weaknesses - Six advisories were published between 6 August and 9 September 2026, including a High-rated SSRF in the delivery worker fixed on 11 August - The status page records API and delivery downtime on 27 August and 22 September 2026, both traced to the hosting provider - The terms give no uptime, latency or support commitment by default. Service levels exist only in a signed Enterprise agreement - Cloud registration requires a Cloudflare Turnstile token and email verification, so an agent can't create an account alone - The API introduction page documents an error shape and `limit` and `offset` pagination that the OpenAPI document doesn't contain ## Before you call it (notes for agents) 1. Use a service token narrowed to one application and an expiry. A root service token covers the whole organisation, and an application secret can delete its application 2. Send your own UUID as `event_id` on `POST /api/v1/event/`. A repeat returns `EventAlreadyIngested` (409), which means the first call succeeded 3. Create the event type before sending. Unknown types fail with `EventTypeDoesNotExist`, and `labels`, `occurred_at` and `payload_content_type` are required 4. Send `payload` as a string, with JSON serialised inside it, up to 512 KiB 5. Set `HOOK0_API_URL` for `hook0-mcp` to the origin without `/api/v1`, and set `HOOK0_READ_ONLY=true` to hide the ten write tools ## Connect Install: ```bash cargo install hook0-mcp ``` First request: ```bash curl -X POST "https://app.hook0.com/api/v1/event" \ -H "Authorization: Bearer $HOOK0_TOKEN" \ -H "Content-Type: application/json" \ -d '{"application_id": "", "event_type": "user.account.created", "payload": "{\"user_id\": 123}", "payload_content_type": "application/json", "labels": {"environment": "tutorial"}, "occurred_at": "2026-10-08T12:00:00Z"}' ``` MCP client configuration: ```json { "mcpServers": { "hook0": { "command": "hook0-mcp", "env": { "HOOK0_API_TOKEN": "your-service-token-here" } } } } ``` Through letme (picks today, calling later): https://letme.dev/hook0. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Hookdeck | BB | 76.9 | 24 | events.webhooks-send | no | https://www.anchorterminal.com/tools/hookdeck.md | | Ably | BB | 75 | 58 | events.webhooks-send | no | https://www.anchorterminal.com/tools/ably.md | | Svix | BB | 74 | 78 | events.webhooks-send | no | https://www.anchorterminal.com/tools/svix.md | | Upstash QStash | BB | 72.3 | 105 | events.webhooks-send | no | https://www.anchorterminal.com/tools/upstash-qstash.md | | Basecamp | B | 67.9 | 220 | events.webhooks-send | no | https://www.anchorterminal.com/tools/basecamp.md | | Plane | B | 67.6 | 229 | events.webhooks-send | no | https://www.anchorterminal.com/tools/plane.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Service tokens are Biscuit tokens that can be narrowed offline to one application, an expiry or a read-only action list, and revoking the root revokes every derived token (source: ) - The `hook0-mcp` server (stdio, MIT, version 3.0.0 of 26 August 2026) is generated from the API snapshot with 23 tools, 13 read and 10 write, and `HOOK0_READ_ONLY` hides the write tools (source: ) - Failed deliveries are retried on a schedule from 3 seconds to 10 hours, 24 retries by default, and deliveries carry an HMAC-SHA256 `X-Hook0-Signature` header (source: ) - Six security advisories were published between 6 August and 9 September 2026, each with the fix commit and the reporter credited, the most severe a High-rated SSRF fixed on 11 August (source: ) - The terms state that no uptime, availability, latency or support response commitment applies by default, and that service levels exist only in a signed Enterprise agreement (source: ) - The site's llms.txt says the MCP server has 17 tools, while the MCP reference and the generated source list 23 (source: ) - Hook0 sends webhooks only. Its own comparison pages say it has no production service for receiving third-party webhooks (source: ) ## Compare - [Ably vs Hook0](https://www.anchorterminal.com/compare/ably-vs-hook0.md): BB 75 vs B 64.6 - [Convoy vs Hook0](https://www.anchorterminal.com/compare/convoy-vs-hook0.md): B 62.2 vs B 64.6 - [Hook0 vs Hookdeck](https://www.anchorterminal.com/compare/hook0-vs-hookdeck.md): B 64.6 vs BB 76.9 - [Hook0 vs Pusher Channels](https://www.anchorterminal.com/compare/hook0-vs-pusher-channels.md): B 64.6 vs D 51.9 - [Hook0 vs Svix](https://www.anchorterminal.com/compare/hook0-vs-svix.md): B 64.6 vs BB 74 - [Hook0 vs Upstash QStash](https://www.anchorterminal.com/compare/hook0-vs-upstash-qstash.md): B 64.6 vs BB 72.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on hook0.com or one of its subdomains, or the README of github.com/hook0/hook0. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "hook0", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Hook0 on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Hook0 on Anchor Terminal](https://www.anchorterminal.com/badges/hook0.svg)](https://www.anchorterminal.com/tools/hook0) ``` Plain link: ```html Hook0 on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Hook0 is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/hook0-dark.png - Light: https://www.anchorterminal.com/assets/share/hook0-light.png