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

MAGI.

Mechanistic interpretability. Activation tracing, circuit discovery, feature attribution under audit.

Agent · Autonomous Org
III
Stable · v0.1.0
2.4s

Overview

The institution sees through itself.

MAGI is the institution's window into its own minds. Where a model produced a verdict, MAGI can trace activations, identify the circuits that fired, and attribute the contribution of features to the result. Glass-box not by hope but by instrumentation. MAGI reports are first-class evidence — MOOT may rely on them, MACE may demand them, MERIT may revoke credentials based on what they reveal.

Methods

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

magi.trace()
Trace activations through a model for a given input. Returns circuit map.
magi:read
magi.attribute()
Compute feature attribution: which inputs caused which output.
magi:read
magi.circuit()
Discover named circuits in a model — induction heads, copy circuits, refusal directions.
magi:admin

Request shape

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

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

Governance posture

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

SLA & metering

2.4s
14s
99.5%
traces

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:

MARC · model snapshots
MIND · activation cache
MAX · every trace
MOTET · circuit catalog
MAXIM · interpretability policy
MEAL · per-trace meter (heavy)

Browse the registry.

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