Aptos MCP
urn:air:aptos.dev:mcp:aptos-mcp
application/mcp-server-card+json
artifact →
- “query Aptos on-chain account data”
- “call Aptos REST APIs from an AI coding assistant”
- “generate Move code with the Aptos MCP server”
AI Catalog manifest · Aptos
Aptos Developer Documentation
Aptos serves an AI Catalog
manifest at /.well-known/ai-catalog.json on aptos.dev, declaring
4 agentic resources
that a discovery service can index without asking anyone’s permission.
Structural grade · AI Catalog 1.0
Near-Conformant
Correctly shaped — every hard check passes — but optional affordances are missing.
ARD conformance-test v0.9.1 (ards-project/ard-spec)
PASS
Run against this exact body with the project’s own
conformance CLI.
Declared identity
404
did:web:aptos.dev —
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-jsondid-web-does-not-resolve
What this manifest advertises
Aptos Agent Skills
urn:air:aptos.dev:skill:aptos-agent-skills
application/agent-skills+json
artifact →
- “write an Aptos Move smart contract”
- “scaffold an Aptos dApp with the TypeScript SDK”
- “audit a Move module for security issues”
Aptos Fullnode REST API
urn:air:aptos.dev:api:fullnode-rest
application/vnd.oai.openapi+json
artifact →
- “get an Aptos account resource via REST”
- “submit a transaction to the Aptos fullnode”
- “look up Aptos REST API OpenAPI endpoints”
Aptos API Catalog
urn:air:aptos.dev:api:catalog
application/linkset+json
artifact →
- “discover Aptos REST and Indexer APIs”
- “find the Aptos OpenAPI spec and health endpoint”
- “list Aptos documentation API entry points”
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— yesAccess-Control-Allow-Origin: *— yes
Evidence. Fetched
https://aptos.dev/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Aptos repository
as ai-catalog/aptos-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.