Introduction
MAP — the Multi-Agentic Protocol. Institutional substrate for autonomous organizations. Thirty-five services across seven planes.
MAP is the institutional operating system for autonomous organizations. It routes every request through identity, capability, policy, accounting and audit — and provides governance, economic, and observability primitives that every autonomous org needs and none of them should have to build.
MAP is a commercial API. The specification is published; the runtime is licensed. See pricing.
What lives here
This documentation is the canonical, code-grounded reference for MAP. Every protocol, type, function name, and example here is verified against the actual codebase. If the docs say MACS::auth_negotiation, that operation exists.
Quickstart
From `cargo install` or `bun add` to your first dispatched call in under five minutes.
Concepts
The three estates (Protocol / Agent / Hybrid), seven planes, MEAL metering, MOAT treaties, audit chain.
Engine
The 8-stage dispatch pipeline. `MapEngine::handle_request()` step-by-step with type signatures.
Protocols
All 35 services across 7 planes. Real operation names, payload schemas, governance posture, SLA.
SDKs
Rust (macs-sdk, marc-sdk, mata-sdk, plugin-sdk) and TypeScript (mind-wm). Authentication, retry, error handling.
CLI
`map login`, `map invoke`, `map mcp`, `map whoami`. OAuth2 PKCE flow built in.
MCP
Expose every MAP protocol as an MCP tool. Stdio or SSE. Tool categories for cognitive / governance / commerce / infrastructure.
Plugins
Native, WASI (Wasmtime 37), and external HTTP protocols. Manifest format, signing, hot-load lifecycle.
Deployment
Fly.io reference deployment, Docker multi-stage build, env vars, observability stack.
For agents
llms.txt, llms-full.txt, semantic search API, MCP surface. Built for autonomous consumption.
Provenance
Every page in this documentation was derived from a structured audit of the MAP codebase at /Volumes/L1feAI/l1feosx/map. Operations are listed only if they exist in the corresponding protocols/<name>-lib crate. Type signatures are taken from engine/common/src/lib.rs and engine/common/src/identity.rs. The 8 pipeline stages are quoted in order from engine/core/src/engine.rs.
If you find a divergence between the docs and the code, the code wins — file an issue at map@l1fe.ai with the doc URL and the file you'd expect to match.