Supabase serves an AI Catalog
manifest at /.well-known/ard.json on supabase.com, declaring
5 agentic resources
that a discovery service can index without asking anyone’s permission.
/.well-known/ard.json — the path ARD v0.91 says a consumer MUST fetch.
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.content-type-not-ai-catalog-jsonhost-identifier-not-did-webThe Supabase MCP server endpoint (streamable HTTP, OAuth-protected) for managing projects, database schema, and queries from MCP clients.
OAuth protected-resource metadata for connecting clients to the Supabase MCP server.
OpenAPI 3.0 description of the Supabase Management API for managing organizations, projects, branches, and configuration.
Index of Supabase documentation and content available as agent-readable markdown.
Agent Skills discovery index for installable Supabase and Postgres skills.
Content-Type: application/json —
yesAccess-Control-Allow-Origin: * —
yeshttps://supabase.com/.well-known/ard.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Supabase repository
as ai-catalog/supabase-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.