/MAKER
4,218 req/slive4.21ms p50
MAP/Registry/24 · MAKER/Plane V · Execution

MAKER.

Native, MCP, A2A, HTTP, WASI — capability-scoped, sandboxed, attested.

Protocol · Stateless
V
Stable · v0.1.0
tool-bound

Overview

A unified surface for every tool.

MAKER is the execution surface. Every tool — native MAP protocol, external MCP server, A2A agent, generic HTTP endpoint, WASI plugin — is invoked through MAKER under a unified envelope: capability scope, sandbox isolation, input attestation, output attestation, audit trace. The agent does not call tools directly; the agent declares an intent, MAKER realizes it under policy and records the outcome.

Methods

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

maker.invoke()
Invoke any tool through the unified envelope. Sandbox, scope, audit applied.
maker:invoke
maker.register()
Register a new tool with the maker registry. Capability declaration required.
maker:admin
maker.attest()
Attest the integrity of a tool's binary or remote endpoint.
maker:admin

Request shape

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

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

SLA & metering

tool-bound
tool-bound
99.95%
invocations

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:

MACS · capability scope
Arsenal · credential proxy
MAX · every invocation
MOTET · tool telemetry
MAXIM · tool policy
MEAL · per-invocation meter
MADE · tool licensing

Browse the registry.

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