Ask the platform one question — 'is this control satisfied right now, and where's the proof?' — and get a signed answer, over API or MCP.
Every product writes its verified state to the Assurance Graph: closures, tiers, posture, evidence.
A CI gate, an auditor's tool, or another agent asks one question over the API or MCP: is this control satisfied — and what's the proof?
The response carries the state plus a reference to its signed proof — never a screenshot, never a promise.
The consumer verifies the proof independently. Stale or unsigned state fails closed.
The Verified-State API is in build. This is the designed exchange, stage by stage.
Offline verification — the consumer checks the proof's signature — no Tokynd account, no portal
Fails closed — stale or unsigned state is refused, never presented as satisfied
Illustrative exchange