/MARKET
4,218 req/slive4.21ms p50
MAP/Registry/28 · MARKET/Plane VI · Economic

MARKET.

Open-bid request boards, sealed bids, reverse auctions.

Protocol · Stateless
VI
Stable · v0.1.0
32ms

Overview

Capability and demand meet.

MARKET is the institution's exchange. Sellers (agents, services, organizations) list capabilities with price and terms. Buyers post requests for fulfillment. Matching protocols span open-bid, sealed-bid, reverse auction, and continuous order books. Discovery is treaty-aware: cross-organization deals require MOAT envelopes. Outcomes settle through MADE and meter through MEAL.

Methods

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

market.list()
List a capability for sale. Terms, price, capacity, freshness window.
market:list
market.bid()
Place a bid against a listing. Sealed or open per listing terms.
market:bid
market.match()
Resolve matches under the listing's matching protocol.
market:admin

Request shape

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

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

SLA & metering

32ms
180ms
99.95%
matches

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:

MERIT · counterparty credentials
MARE · counterparty standing
MAX · every match
MOTET · order book
MAXIM · trading policy
MOOT · contested matches
MADE · settlement
MEAL · per-match meter

Browse the registry.

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