MADE.

x402-native, multi-rail, receipts pinned to the audit chain.

Service kind

Hybrid · Protocol + Agent

Plane

Status

Stable · v0.1.0

p50 · settlements · bps

rail-bound

Overview

Settlement, witnessed.

MADE is the settlement layer for agent commerce. Native integration with x402 for HTTP-mediated micropayments; multi-rail support across L1s, L2s, and traditional payment processors. Every payment is policy-checked by MAXIM, metered by MEAL, recorded by MAX. Cross-organization payments flow under MOAT treaties. The institution issues, spends, settles — and never loses the receipt.

Methods

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

made.invoice()

Generate an invoice — caller, payer, amount, rail, terms.

made:invoice

made.settle()

Execute settlement on a selected rail. Returns proof-of-settlement.

made:settle

made.refund()

Issue a refund under terms or arbitration. Auditable inverse of settle.

made:admin

Request shape

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

// POST /v1/protocol/made.invoice // MAP envelope (provided by MACS): { "caller": "did:oas:l1fe:agent:0xa3f…", "capability": "made:invoice", "signature": "ed25519:0x9c…", "trace": "00-4f81b3a…-…-01" } // MADE body (example): { "intent": "Settlement, witnessed.", "budget": { "tokens": 200000, "deadline_ms": 8000 }, "return": ["result", "audit"] } // Response: { "result": "…", "audit": "max://record/0x4f81b3a-made-7a…" }

Governance posture

Every hybrid 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("made.invoice", body, { capability }); // 2. MCP tool — any MCP-compliant client await mcp.call("map.made.invoice", body); // 3. A2A task — cross-organization invocation await a2a.task("map://intent", { intent: body, treaty: "moat://0x91a" });

SLA & metering

p50 latencyrail-bound

p99 latencyrail-bound

availability99.95%

billing unitsettlements · bps

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:

ConsultsMAXIM · payment policy
MOAT · cross-org terms
MANA · runway

Records toMAX · every settlement
MOTET · payment telemetry

Subject toMAXIM · transaction policy
MOOT · refund disputes

Settled withMEAL · self-meter (basis points)

Browse the registry.

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

All Protocols→Request API access→