(no displayName)
urn:air:artie.com:mcp:artie
application/mcp-server-card+json
artifact →
AI Catalog manifest · Artie
Artie
Artie serves an AI Catalog
manifest at /.well-known/ai-catalog.json on artie.com, declaring
1 agentic resource
that a discovery service can index without asking anyone’s permission.
Structural grade · AI Catalog 1.0
Flavored
Fails a hard check in the data model. A catalog in spirit rather than in schema.
ARD conformance tool v0.5.0
FAIL
Run against this exact body with the project’s own
conformance CLI — 1 critical error.
Declared spec version
1.0
The
specVersion in the manifest. AI Catalog 1.0 is current; anything lower is an earlier draft.
⚠ Hard checks failed. An ARD client cannot assume this manifest parses to the model the specification defines.
entry-no-descriptionentry-no-displayNameno-host-object
Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
content-type-not-application-jsoncors-not-wildcardentry-no-representativeQueries
What this manifest advertises
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— no — servesapplication/ai-catalog+jsonAccess-Control-Allow-Origin: *— no — header absent
Evidence. Fetched
https://artie.com/.well-known/ai-catalog.json on 2026-07-31, HTTP
200. The verbatim body is stored alongside its manifest in the
Artie repository
as ai-catalog/artie-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.