SurrealDB serves an AI Catalog
manifest at /.well-known/ai-catalog.json on surrealdb.com, declaring
10 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.
Declared identity
404
did:web:surrealdb.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
10 entries
6 media types
26 representative queries
0 trust manifests
Host identifier: did:web:surrealdb.com
What this manifest advertises
SurrealDB MCP Server
urn:air:surrealdb.com:mcp:cloud
Managed Model Context Protocol server for SurrealDB Cloud. Deploy and manage instances and contexts, run SurrealQL against cloud instances, manage organisation access and billing, and connect agent memory - from any MCP-compatible client.
“list my SurrealDB Cloud organisations and instances”
“check the status, metrics, and logs of my SurrealDB instance”
SurrealDB A2A Agent Card
urn:air:surrealdb.com:mcp:agent-card
A2A Agent Card for the SurrealDB Cloud MCP server: the skills it offers, the interface it is reachable on, and both authentication paths - Surreal ID OAuth and a personal access token. The service speaks MCP rather than an A2A transport binding, so a client finding no supported binding should connect over MCP.
Curated llms.txt overview of the SurrealDB platform - the multi-model database engine, agent memory layer, distributed storage, SurrealDB Cloud, and SurrealDB Studio - with links to canonical pages. Every page on the site also supports markdown content negotiation via 'Accept: text/markdown' or a '.md' path suffix.
“load the full SurrealDB website content as context”
“explain SurrealQL and SurrealDB features in depth”
“detailed reference on SurrealDB products, features, and use cases”
SurrealDB Agent Skills index
urn:air:surrealdb.com:skills:index
Agent Skills discovery index for SurrealDB, listing every published SKILL.md with a sha256 digest over the bytes served alongside it. Covers the CLI, the JavaScript and Python SDKs, SurrealKit, SurrealQL with its functions and query performance, and vector search.
“find documentation and status pages for SurrealDB services”
SurrealDB agent authentication guide
urn:air:surrealdb.com:agent:auth
How an agent obtains and uses a credential for SurrealDB: Surreal ID OAuth with dynamic client registration for interactive clients, and personal access tokens for unattended ones, with the scopes each surface needs.
“find the URL of a SurrealDB blog post or product page”
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://surrealdb.com/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
SurrealDB repository
as ai-catalog/surrealdb-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.