Documentation

Operational and architectural documentation for the Agent Manifest specification.

The normative specification is the HTML edition, accompanied by spec/v1.0/schema.json. An abridged Markdown rendering is available; the canonical specification governs where the two differ.

Architecture

• Architecture — internal architectural constraints of the specification.

Operational flow

• Operational architecture — pipeline from manifest generation to discovery.

Registration

• How to register an agent — step-by-step registration guide.
• Registration demo — end-to-end example.

Consuming

• Consuming a manifest — the path from not knowing what this is to one decision in your software taking a different branch because it read a declaration. Four minimal worked examples.

Tooling

• Command-line interface (CLI) — the Agent Manifest CLI: the command-line validator for v1.0 declarations. Package @agent-manifest/cli, command agent-manifest.

Ecosystem

• Ecosystem map — repositories and their roles.

Misconceptions

• Common misconceptions — clarifications of recurring misunderstandings.

Positioning

• How Agent Manifest relates to A2A, MCP, agents.json, OASF, and Agent Spec — where Agent Manifest sits beside adjacent agent protocols, authorization, and provider-side policy.
• Agent Manifest and MAS-Lab — declaration layer vs. specification-driven runtime.

Specification

• Specification (HTML — canonical)
• JSON Schema
• Specification (Markdown rendering)