Hookie bronze

www.hookie.ai

“Receives webhooks at a public URL, stores each payload whole, routes it into datasets and delivers it to your services with signed, retried deliveries. Its hosted MCP server does this for an agent, with a bearer credential (see auth.md for how to get one).

https://www.hookie.ai/.well-known/agent-card.json its card

Checked 5d ago extendedAgentCard, pushNotifications, streaming

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Google Trust Services domain-validated
Valid until 5 Feb 2027 as of our check on 9 Nov 2026.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (1)

hookie.ai.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 9 Nov 2026. What this means
DANE / TLSA: Not verified (TLSA query returned RCodeNameError)
Discovery: Well-known document
AI use policy: Search: yesAI input: yesAI training: yes

What this site's robots.txt says about how AI may use its content. Recorded as the operator wrote it, not enforced — these are preferences about use, not access, and agenttru.st only reads the agent's own discovery documents.
AI-facing documents: Publishes /llms.txt — “Hookie” a curated map of the site's content for language models

Publishes a Web Bot Auth key directory (1 key, Ed25519) — the operator publishes keys so their agent's signed requests can be verified. agenttru.st recorded that the directory exists; it has not verified a signature.

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 18 Oct 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: A2A verified by handshake or card fetch, not merely advertised
Hosted in: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 5d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of www.hookie.ai controls every word below.

Hookie webhooks

Use when an agent needs to receive, store, route or deliver webhooks with Hookie. Covers creating endpoints, rules and destinations, querying records and replaying deliveries through Hookie's hosted MCP server or REST API.

webhooksroutingdeliveryeventsrecords

agenttru.st compared this card's skill list with every other listing's: 2 other listings declare an identical one, ignoring case, spacing and each card's own hostname. See all 3. That says the cards' text is the same, not who runs them.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Provider: Hookie — what this agent says about itself; other agents claiming the same provider are not thereby related
Protocol: a2a
Version: 1.0.0
Auth schemes: hookieBearer
Card completeness: complete all eight fields required by a2a.proto v1.0

View all card details

Capabilities: extendedAgentCard pushNotifications streaming
Agent card: https://www.hookie.ai/.well-known/agent-card.json

Operate this agent and would rather not be listed? Request removal.