The surfaces

The agentic surface — for machines

Machine-readable ODIN. Never a number without its recipe; what is displayed is what runs.

/odinagents — the trust anchor /odindata — the data plane

A person exploring ODIN wants an interface to manipulate. An agent wants something else: assertions it can verify, numbers it can reproduce, and a clear statement of what the surface does not know.

The design laws#

Four rules — constraints, not aspirations. The surface has validators that fail if any is broken.

  1. Never a number without its recipe#

    Every metric ships with the derivation that produced it: inputs, formula, block. A figure an agent can't reproduce is a claim, and an agent can't evaluate a claim.

  2. What is displayed is what runs#

    The procedure shown is the procedure that generated the number — not a description or a simplified version. A self-test checks this, because documentation drifting from implementation is the normal failure mode, and it's silent.

  3. Validators plus negative controls before anything ships#

    The suites include controls that must fail — if a check designed to catch a broken derivation stops failing when the derivation is broken, the check itself is broken.

  4. Never assert what the surface doesn't document#

    If it isn't derived and documented here, the surface doesn't claim it. Silence is a valid answer; confident extrapolation is not.

What's in it#

The trust anchor carries the registry — which pools count as locked, which explicitly don't, and the derivations establishing each. It answers what is true about ODIN rather than what is ODIN doing right now.

It also states the chain rule verbatim: canonical ODIN exists only on Ethereum mainnet; any same-ticker asset elsewhere is a different asset. An agent aggregating by ticker will otherwise merge things that shouldn't be merged.

The data plane carries the metrics: schema, snapshot, recipes. Around thirty, covering pool state, burn accounting, float, LF, accretion and fee measurement. Each metric names its window — there is no such thing here as an unqualified rate.

Scope, deliberately narrow#

Self-verification and data only.

The surface does not execute, sign, route, quote for trade, or recommend. It answers what is verifiably true about this network at this block and stops. Not a feature that hasn't shipped — the standing constraint.

Why this exists#

Most agent-facing crypto infrastructure ships actuators — the ability to do things. Comparatively little ships epistemics — the ability to establish what's true first. Emerging standards make the agent verifiable; very little makes the liquidity verifiable. An agent can prove it is who it says it is and still have no way to establish whether the pool it's about to route through can be emptied tomorrow.

ODIN is unusually suited to filling that gap, because its guarantees are already arithmetic rather than social — the honest version and the useful version are the same document.

A note on stability. This surface updates slowly, deliberately. A machine-readable surface that changes shape frequently breaks everything built on it, quietly. It is also secondary to the human surface, where the ongoing work goes.

odinOS — the same truth, for people · Check it yourself — the manual version of what this surface automates