AI Catalog manifest · Hookdeck

Hookdeck

Hookdeck serves an AI Catalog manifest at /.well-known/ai-catalog.json on hookdeck.com, declaring 6 agentic resources that a discovery service can index without asking anyone’s permission.

Open the live manifest → Hookdeck provider profile

Structural grade · AI Catalog 1.0

Near-Conformant

Correctly shaped — every hard check passes — but optional affordances are missing.

ARD conformance-test v0.9.1 (ards-project/ard-spec)

PASS

Run against this exact body with the project’s own conformance CLI.

Declared identity

404

did:web:hookdeck.com — resolving it returns 404. A did:web: that does not resolve is a string, not an identity, and does not earn the identity affordance here.

Discovery path

predecessor

Answered only at /.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.

Declared spec version

1.0

The specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.

Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.

content-type-not-ai-catalog-json
did-web-does-not-resolve

6 entries

3 media types

18 representative queries

0 trust manifests

Host identifier: did:web:hookdeck.com

What this manifest advertises

Hookdeck Event Gateway API

urn:air:hookdeck.com:api:event-gateway

REST API for inbound webhook infrastructure: sources, destinations, connections, transformations, events, requests, attempts and issues.

application/json artifact →

“receive webhooks from a third party reliably”
“retry a failed webhook delivery”
“route incoming webhook events to different endpoints”

Hookdeck Outpost API

urn:air:hookdeck.com:api:outpost

REST API for outbound event delivery to customer destinations: tenants, destinations, topics, publishes, events and delivery attempts.

application/yaml artifact →

“send webhooks to my own customers”
“deliver events to a customer AWS SQS queue or Kafka topic”
“add per-tenant webhook destinations to my platform”

Hookdeck Console API

urn:air:hookdeck.com:api:console

API for creating and reading Hookdeck Console test URLs that capture HTTP requests without an account.

application/json artifact →

“create a temporary URL to capture a webhook”
“inspect a webhook payload without signing up”
“debug an inbound HTTP request without deploying a server”

Hookdeck Agent Skills

urn:air:hookdeck.com:skills:index

Agent Skills discovery index for the hookdeck, event-gateway and outpost skills.

application/json artifact →

“install the Hookdeck agent skill”
“get instructions for building with Hookdeck webhooks”
“set up outbound webhook delivery with the Outpost skill”

Hookdeck Event Gateway docs

urn:air:hookdeck.com:docs:event-gateway

Documentation index for Hookdeck Event Gateway: product docs, guides, API reference and CLI, with Markdown URLs.

text/plain artifact →

“how do I create a Hookdeck connection”
“Hookdeck Event Gateway API reference in markdown”
“verify webhook signatures with Hookdeck”

Hookdeck Outpost docs

urn:air:hookdeck.com:docs:outpost

Documentation index for Hookdeck Outpost: outbound delivery, destinations, topics, API reference and self-hosting, with Markdown URLs.

text/plain artifact →

“how do I send webhooks to my customers with Outpost”
“Outpost self-hosting documentation”
“Outpost API reference in markdown”

How it is served

The publishing guide asks for three things at the transport layer, because a crawler is the consumer that matters and a crawler is a browser-shaped client.

HTTPS only — yes (HTTP 200)
Content-Type: application/json — yes
Access-Control-Allow-Origin: * — yes

Evidence. Fetched https://hookdeck.com/.well-known/ai-catalog.json on 2026-09-13, HTTP 200. The verbatim body is stored alongside its manifest in the Hookdeck repository as ai-catalog/hookdeck-ai-catalog.json. Nothing on this page is derived or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not exist, which makes it — like an A2A Agent Card — one of the few agent artifacts that cannot be produced on a provider’s behalf. Grades are recomputed on every build; the specification is a v0.9 draft and these verdicts will move when it does.

Work with this as data

Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for agent discovery

3 MCP tools reach this

apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

Search the catalog

curl "https://apis.io/api/v1/search?q=hookdeck&limit=10"

Everything under a tag

curl "https://apis.io/api/v1/tags/hookdeck"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.