The Ticket Fairy serves an AI Catalog
manifest at /.well-known/ai-catalog.json on ticketfairy.com, declaring
8 agentic resources
that a discovery service can index without asking anyone’s permission.
Run against this exact body with the project’s own
conformance CLI.
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
host-identifier-not-did-web
8 entries
4 media types
25 representative queries
0 trust manifests
Host identifier: urn:air:ticketfairy.com
What this manifest advertises
Ticket Fairy MCP Server
urn:air:ticketfairy.com:server:mcp
Model Context Protocol server for managing events, ticket types, orders and sales. It ships inside the Ticket Fairy command-line tool (npm install -g ticketfairy) and runs locally over stdio. The linked document names the package, the command and the transport.
“does Ticket Fairy support RFID wristbands and cashless payments”
“which payment methods and countries does Ticket Fairy support”
“how does Ticket Fairy stop ticket scalping”
“can I sell tickets from my own website with Ticket Fairy”
Event and Page Index
urn:air:ticketfairy.com:index:sitemap
Sitemap index covering every listed event, city guide, venue guide and page on the platform, split into per-country files. Each page it names also answers in Markdown: add .md to its URL, or send Accept: text/markdown.
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://ticketfairy.com/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
The Ticket Fairy repository
as ai-catalog/the-ticket-fairy-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.
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.
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.