MARS.

Datasets, models, contracts, real things — registered with provenance and rights.

Service kind

Protocol · Stateless

Plane

VII

Status

Stable · v0.1.0

p50 · registrations · resolutions

12ms

Overview

Every asset of standing.

MARS is the institution's directory of standing. Every asset that matters — dataset, model, charter, treaty, real-world thing under digital twin — is registered with provenance (where did it come from), rights (who may use it, on what terms), and integrity (cryptographic anchor). MARS is the address book of the autonomous; without it, there are no recoverable references, only ephemeral ones.

Methods

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

mars.register()

mars:register

mars.resolve()

Resolve an asset by canonical name. Returns current metadata and integrity proof.

mars:read

mars.update()

Update registry metadata (not the underlying asset). Versioned.

mars:admin

Request shape

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

// POST /v1/protocol/mars.register // MAP envelope (provided by MACS): { "caller": "did:oas:l1fe:agent:0xa3f…", "capability": "mars:register", "signature": "ed25519:0x9c…", "trace": "00-4f81b3a…-…-01" } // MARS body (example): { "intent": "Every asset of standing.", "budget": { "tokens": 200000, "deadline_ms": 8000 }, "return": ["result", "audit"] } // Response: { "result": "…", "audit": "max://record/0x4f81b3a-mars-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("mars.register", body, { capability }); // 2. MCP tool — any MCP-compliant client await mcp.call("map.mars.register", body); // 3. A2A task — cross-organization invocation await a2a.task("map://intent", { intent: body, treaty: "moat://0x91a" });

SLA & metering

p50 latency12ms

p99 latency60ms

availability99.99%

billing unitregistrations · 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:

ConsultsOAS · owner identity
MERIT · owner standing

Records toMAX · every registration
MOTET · registry growth

Subject toMAXIM · registration policy

Settled withMEAL · per-registration meter

Browse the registry.

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

All Protocols→Request API access→