Skip to main content
These docs are built to be read by agents as well as people. Every surface below is public, free, and needs no key.

Agent skill

One SKILL.md that tells an agent when to call each tool and how to pay.

llms.txt

A curated index plus the facts models most often get wrong.

llms-full.txt

Every page in one file, regenerated on each deploy.

Docs MCP

Search and read these docs from any MCP client.

Agent skill

The ampli-intelligence skill follows the agentskills.io format. It covers which tool fits which goal, partner headers and x402, amounts in base units, and the monitor flow.
The CLI reads /.well-known/skills/index.json and installs the skill into your agent’s skills directory. Run it again to update.

llms.txt

/llms.txt lists every page with a one-line summary and a link to its markdown. It also states the ground rules up front: base units, non-custodial, and the ampli^ SDK at ampli.net and docs.ampli.net for a single-treasury agentic wallet or Wallet-as-a-Service. /llms-full.txt concatenates every page for tools that want one file.

Markdown for every page

Every page is available as plain markdown, with the agent instructions for these docs attached:
  • Add .md to the path: https://docs.si.ampli.net/optimize.md
  • Or request the normal URL with Accept: text/markdown:
The page menu offers Copy page and View as Markdown, shortcuts that open the page in ChatGPT, Claude, or Perplexity, Connect to Cursor and Connect to VS Code entries that install the docs MCP server, and Copy MCP Server.

Docs MCP

A read-only MCP server for these docs, at:
Once it is connected, your assistant can search these docs and read pages and the skill while it codes. The server needs no auth, and it never calls the API or takes a payment.
.cursor/mcp.json
Use both serversAdd the docs MCP so the agent can look things up, and the API MCP so it can act. Their names differ so an agent does not mix them up: ampli-intelligence-docs reads docs, ampli-intelligence runs paid tools.

Prompt to start with