/OAS
4,218 req/slive4.21ms p50
MAP/Registry/02 · OAS/Plane I · Identity

OAS.

Vendor-neutral W3C-DID identity with lineage to a human root. Offline-verifiable, eleven entity kinds.

Adapter · External Standard
I
Stable · v0.1.0
8ms

Overview

The passport system for autonomous entities.

OAS is the open identity standard MAP adopts. Every entity in the mesh — agent, tool, skill, workflow, model, dataset, service, agent-instance — gets a did:oas:<namespace>:<kind>:<identifier>. Every agent traces back to a human root through cryptographically-signed lineage. MAP is OAS's consumer, never its keeper. The specification lives at openagent.id; the verification work lives in MACS.

Methods

Every method is dispatched through MAP. Capability scope, policy, and accounting apply uniformly.

oas.resolve()
Resolve a did:oas to its current document. Verification of returned document is the caller's responsibility.
oas:read
oas.lineage()
Walk lineage to the human root. Returns full chain with signatures intact for offline verification.
oas:read
oas.capabilities()
Enumerate declared capabilities of a DID. MACS uses this to bound the capability set.
oas:read

Request shape

A canonical call. Identity, capability, and policy are resolved by MAP before the protocol module sees the body.

// POST /v1/protocol/oas.resolve // MAP envelope (provided by MACS): { "caller": "did:oas:l1fe:agent:0xa3f…", "capability": "oas:read", "signature": "ed25519:0x9c…", "trace": "00-4f81b3a…-…-01" } // OAS body (example): { "intent": "The passport system for autonomous entities.", "budget": { "tokens": 200000, "deadline_ms": 8000 }, "return": ["result", "audit"] } // Response: { "result": "…", "audit": "max://record/0x4f81b3a-oas-7a…" }

Governance posture

Every protocol in MAP is bound by the same governance posture. Refusal carries reasons. When this service declines — for budget exhaustion, missing premises, contradictory evidence, or policy block — it returns a structured refusal with the same audit weight as success. Refusals are first-class records; they are not silences.

Dissent is preserved. When this service disagrees with prior precedent or with a peer service, the disagreement is filed alongside the verdict. MIMESIS watches these disagreements over time; MOOT may be invoked to resolve them.

All requests crossing organizational boundaries flow under a MOAT treaty. The treaty fixes capability scope, rate, and economic terms. Calls outside the treaty's envelope are refused at MACS.

Integration

Three integration surfaces. All requests pass through MAP.

// 1. Native MAP protocol (signed envelope) await map.dispatch("oas.resolve", body, { capability }); // 2. MCP tool — any MCP-compliant client await mcp.call("map.oas.resolve", body); // 3. A2A task — cross-organization invocation await a2a.task("map://intent", { intent: body, treaty: "moat://0x91a" });

SLA & metering

8ms
40ms
99.95%
resolutions

Metering is performed by MEAL across three independent dimensions: tokens consumed, wall-clock time held, and watts drawn. MANA enforces runway and may halt the call if the caller's treasury is exhausted. See pricing for current rate cards.

Adjacent

This service does not stand alone. The protocols it consults and feeds:

MAX · resolution events
MARS · DID registry
MEAL · per-resolution meter

Browse the registry.

Thirty-five protocols, each with its own contract. Identity to awareness, in seven planes.