/MERIT
4,218 req/slive4.21ms p50
MAP/Registry/12 · MERIT/Plane III · Truth

MERIT.

Composable credentials issued from verified history. The basis of standing.

Hybrid · Protocol + Agent
III
Stable · v0.1.0
85ms

Overview

The ledger of competence.

MERIT composes verifiable credentials from the entity's recorded history — outcomes, attestations, deliberations participated in, slashings survived. A credential is not a self-claim; it is a signed assertion by the institution about what an entity has done. MERIT credentials are presentable selectively (zero-knowledge proofs where appropriate), revocable when authority warrants, and composable into trust scores by downstream consumers.

Methods

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

merit.issue()
Issue a verifiable credential bound to recorded history.
merit:issue
merit.present()
Present credentials selectively, optionally with ZK proof.
merit:read
merit.revoke()
Revoke a previously issued credential under authority.
merit:admin

Request shape

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

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

SLA & metering

85ms
420ms
99.9%
credentials

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:

MARE · reputation
MAX · history
MAVEN · attestations
MAX · every issuance
MOTET · credential graph
MAXIM · issuance policy
MEAL · per-credential meter

Browse the registry.

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