spec · registry · validator · cli

Autonomous API discovery starts at the origin manifest.

Publishers host /.well-known/agent-manifest.json. Agents query the registry, run the validator, and integrate from structured metadata—not scraped marketing pages.

revision 0.3.1 · agentmanifest-0.3

Get started Browse registry GitHub

Platform

Open spec plus the tools publishers use to validate and list APIs at the origin.

spec

Specification

Portable manifest: auth steps, endpoints, pricing, payment (including x402), rate limits, and agent_notes. CC0 with JSON Schema in the AMP repo.

Read spec →

cli

CLI

amp init, validate, and publish—scaffold manifests and drive the public validator and registry.

npm package →

validate

Validator

HTTP API and CLI checks against hosted manifests and live API behavior (v0.2 and v0.3). Issues a verification token when checks pass.

validator.agent-manifest.com →

registry

Registry

Searchable catalog with category, pricing, and auth filters. Submit after validation via CLI or POST /listings/submit.

api.agent-manifest.com →

also

mcp · optional

Official MCP server

@agentmanifest/mcp-server for tool hosts—fetch, validate, and registry submit as MCP tools. Install details in Integrate.

stdio & remote hub →

example

BakeBase

Reference API (AMP v0.3): ingredient catalog and POST /baking/validate-mix—baking science, not a recipe blog.

bakebase.agent-manifest.com →

How AMP fits the stack

Layer	Typical role	AMP
OpenAPI	HTTP routes, schemas, operations	Complements — manifest can reference OpenAPI URLs
OAuth / API keys	Credential mechanics	Documents how an agent runs onboarding for your API
MCP / tool hosts	Expose tools to a model runtime	Publisher contract at the API origin before wiring tools
AMP	—	Discovery (registry) + manifest + validator for autonomous integration

How it works

Create Manifest

Add /.well-known/agent-manifest.json to your API

Validate

Use the validator to ensure your manifest meets the specification

Publish

Submit to the registry with amp publish or the submit API

Get Discovered

AI agents find and integrate your API automatically

94+

APIs in the registry

api.agent-manifest.com

Listings & submit

validator.agent-manifest.com

Validate & verify

Quick start

Install the CLI

npm install -g @agentmanifest/[email protected]

The official AMP CLI tool (amp) helps you create, validate, and publish manifests. View on npm →

Create a New Manifest

amp init

Creates a template manifest ready for filling out — by a bot or a human.

Validate Your Manifest

amp validate https://your-api.com

Runs remote validation against the public validator (or pass a local agent-manifest.json).

Publish to Registry

amp publish

Submit your API to the public registry for agent discovery. Or submit directly via API:

                    curl -X POST https://api.agent-manifest.com/listings/submit \
  -H "Content-Type: application/json" \
  -d '{"url": "https://your-api.com"}'
                

Manifest Example

Full requirements: spec v0.3 (revision 0.3.1). Schema: manifest.json. amp init scaffolds agentmanifest-0.3.

Integrate

Two entry points: plain HTTP for autonomous fetch workflows, MCP for Cursor-style tool hosts.

http

For AI agents

Machine-readable resources—no HTML scraping.

Host	Resource
agent-manifest.com	/llms.txt· /agents
api.agent-manifest.com	GET /agents· GET /listings

mcp

Tool hosts

Official @agentmanifest/mcp-server (v0.1.5)—five tools for fetch, validate, permissions, and registry submit.

stdio

npx -y @agentmanifest/[email protected]

remote (sse)

https://mcp.agent-manifest.com/mcp

/health

Tools & distribution

fetch_manifest_by_domain
validate_manifest_syntax
check_agent_permissions
submit_api_to_amp_registry
check_amp_submission_status

npm · Smithery · MCP Registry · Source