The Missing Layer Between APIs and Autonomous Agents

OpenAPI describes endpoints. OAuth describes auth. Nothing describes how an agent discovers, authenticates, and integrates an API at runtime.

AMP defines that layer.

Executable metadata, not documentation.

Get Started View on GitHub

The Gap in Today's Stack

OpenAPI describes endpoints — not how agents use them.
OAuth describes auth — not how agents run the flow.
Agents require manual wiring or hardcoded integrations.

There is currently no interoperable standard for autonomous API onboarding.

AMP is an open protocol for autonomous API onboarding.

A machine-readable manifest located at /.well-known/agent-manifest.json declares authentication flows, capabilities, pricing, and operational expectations.

An agent can fetch the manifest, execute the auth flow, traverse the API, and retrieve live data — without human configuration.

AMP is transport-agnostic and compatible with existing API standards. Designed to complement OpenAPI and OAuth — not replace them.

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

Submit

Get Discovered

AI agents find and integrate your API automatically

Demonstrated Autonomous Integration

Independent autonomous agents have successfully:

✓ Discovered live AMP manifests
✓ Executed authentication flows
✓ Traversed documented routes
✓ Retrieved production data

Without manual configuration or hardcoded integrations.

These integrations were performed without prior hardcoded knowledge of the target APIs.

Quick Start

Install the CLI

npm install -g @agentmanifest/cli

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

Ensures compliance with the specification

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

See the spec for full requirements. v0.3 is the current spec — build on it. amp init still outputs v0.2 for now; those manifests work with the validator and registry. v0.3 CLI update coming soon.

Core Services

⚡

CLI Tool

Official command-line tool for creating, validating, and publishing manifests. Creates a template ready for filling out — by a bot or a human.

npm package →

✓

Validator

Validate your agent-manifest.json for compliance with the specification. Supports v0.2 and v0.3. Available as NPM package, CLI tool, and web API.

validator.agent-manifest.com →

📚

Registry

Public searchable catalog of AMP-compliant APIs. Filter by category, pricing model, authentication, and more.

api.agent-manifest.com →

🥖

BakeBase

Reference implementation demonstrating AMP compliance. AI-first food science API with real chemistry calculations.

bakebase.agent-manifest.com →

Two Levels of Categorization

AMP uses two levels to help agents discover and filter APIs: primary_category (what kind of API) and categories (domain expertise).

primary_category

Functional type — how the API is used

reference live computational transactional enrichment personal discovery