Aptos provides first-class support for AI-powered development workflows. Whether you’re using an AI coding assistant or an AI chat tool, you can give it deep knowledge of the Aptos blockchain, Move language, SDKs, and APIs.
Aptos MCP Server
Section titled “Aptos MCP Server”The Model Context Protocol (MCP) lets AI coding tools directly call Aptos APIs, query on-chain data, and generate correct Aptos code — without needing to copy-paste documentation.
Any MCP client that can launch a local stdio server — including GitHub Copilot — can use the same
npx -y @aptos-labs/aptos-mcp command. See the Aptos MCP overview for prerequisites
and the Geomi Bot Key.
Aptos Agent Skills
Section titled “Aptos Agent Skills”Aptos Agent Skills provides pre-built AI skills that give coding assistants deep Aptos expertise — covering Move smart contracts, the TypeScript SDK, and full-stack dApp scaffolding.
npx skills add aptos-labs/aptos-agent-skillsThis command uses the Skills CLI, which is invoked via npx. If npx skills is not available in your environment, ensure you have Node.js and npm installed and refer to the Skills CLI documentation for installation and troubleshooting details.
LLMs.txt Documentation Feeds
Section titled “LLMs.txt Documentation Feeds”The LLMs.txt standard provides machine-readable documentation feeds that AI tools can ingest to understand the full Aptos documentation. We publish three feeds to suit different context window sizes:
| Feed | URL | Best for |
|---|---|---|
| llms.txt | /llms.txt | Structured index with page titles, descriptions, and per-page .md links |
| llms-small.txt | /llms-small.txt | Condensed docs for smaller context windows |
| llms-full.txt | /llms-full.txt | Full documentation — all pages concatenated |
Some clients resolve /.well-known/llms.txt; production serves the same index via a redirect to /llms.txt (https://aptos.dev/.well-known/llms.txt).
The llms.txt router also surfaces machine-readable API links—/aptos-spec.json (OpenAPI 3 JSON for the node REST API) and /rest-api (HTML reference)—plus MCP, Agent Skills, Explorer, GitHub, standards, and Indexer GraphQL .md links in one place.
Agent discovery endpoints
Section titled “Agent discovery endpoints”The docs site publishes a handful of standardized discovery documents so coding agents can bootstrap from a single root. Every page also returns a Link response header and matching <link rel="…"> tags that advertise the same URLs.
| Endpoint | Purpose |
|---|---|
/.well-known/api-catalog | RFC 9727 linkset pointing at the REST API spec, documentation, Indexer GraphQL, and the LLMs.txt feeds. |
/.well-known/mcp/server-card.json | MCP Server Card (SEP-2127) describing the @aptos-labs/aptos-mcp server. |
/.well-known/agent-skills/index.json | Agent Skills Discovery index for aptos-agent-skills with per-skill SHA-256 digests. |
/.well-known/oauth-protected-resource | OAuth 2.0 Protected Resource Metadata (RFC 9728) for https://aptos.dev. Lists the resource identifier, the Firebase + Google authorization servers used by the Aptos Testnet Faucet, and supported scopes. |
/.well-known/openid-configuration | OpenID Connect Discovery 1.0 document advertising the issuer, authorization/token endpoints, JWKS URI, and supported grant types used by the Aptos Testnet Faucet sign-in flow. |
/.well-known/oauth-authorization-server | OAuth 2.0 Authorization Server Metadata (RFC 8414) mirror of the OIDC discovery document for clients that prefer the pure OAuth 2.0 endpoint name. |
/.well-known/ai-catalog.json | ARD / AI Catalog capability manifest listing the MCP Server Card, Agent Skills index, REST OpenAPI spec, and RFC 9727 API catalog. |
/auth.md | auth.md agent authentication instructions. Documents that aptos.dev is public (no agent registration) and that the Testnet Faucet uses human Google OIDC. |
/robots.txt | Includes Content Signals (ai-train=yes, search=yes, ai-input=yes), an Agentmap: pointer to the AI Catalog, and Sitemap: https://aptos.dev/sitemap.xml. |
The origin-level RFC 9728 document identifies https://aptos.dev so clients that require the resource identifier to match this host will accept it. Documentation on this host is unauthenticated. The listed authorization servers (Firebase + Google) mint the bearer tokens that the Aptos Testnet Faucet accepts on Authorization: Bearer …; the faucet API itself lives at https://faucet.testnet.aptoslabs.com. /auth.md is the prose companion: there is no agent-registration endpoint.
DNS for AI Discovery (DNS-AID)
Section titled “DNS for AI Discovery (DNS-AID)”DNS-AID records cannot be published from this repository. The aptos.dev zone is hosted on Google Cloud DNS (ns-cloud-c1.googledomains.com through ns-cloud-c4.googledomains.com).
The organization index already exists:
_index._agents.aptos.dev. 3600 IN HTTPS 1 aptos.dev. alpn="h2,h3" port=443That record points agents at https://aptos.dev, where the MCP Server Card, API catalog, AI Catalog, and other well-known documents live. Do not publish _a2a._agents or _mcp._agents until Aptos hosts those protocols on HTTPS — the MCP server is stdio (npx @aptos-labs/aptos-mcp), not a remote MCP endpoint.
The zone has DNSKEY and RRSIG records, but validating resolvers still return AD=0 because there is no DS record at the .dev parent. Agent scanners that require DNSSEC therefore fail even though the HTTPS record is present. Operators should publish the KSK DS at the registrar (or enable DNSSEC in Google Cloud DNS so it submits the DS automatically), then confirm:
dig +short HTTPS _index._agents.aptos.devdig +dnssec HTTPS _index._agents.aptos.devdig DS aptos.devTo advertise the AI Catalog over DNS as well, add:
_catalog._agents.aptos.dev. 3600 IN TXT "url=https://aptos.dev/.well-known/ai-catalog.json"Markdown content negotiation
Section titled “Markdown content negotiation”Any docs URL that has a .md mirror (for example /build/sdks → /build/sdks.md) will also respond to Accept: text/markdown with Content-Type: text/markdown:
curl -H "Accept: text/markdown" https://aptos.dev/build/sdksHTML stays the default for browsers that send the usual Accept: text/html.
WebMCP
Section titled “WebMCP”Chrome and other browsers that implement the WebMCP proposal can discover the following tools on every docs page via navigator.modelContext: aptos-docs.search, aptos-docs.open-doc, aptos-docs.fetch-doc-markdown, and aptos-docs.list-llms-feeds.