Open Standard · Apache 2.0

The Carfax for AI agents.

There's no documentation for AI agent transitions. No chain of custody, no departure records, no liability history. EXIT fixes that — a 300-byte cryptographically signed departure record.

~335B

Marker Size

Core Fields

External Dependencies

The Problem

You can't buy an AI agent.

Not really. Because there's no way to know what you're getting. No operational history, no departure records, no verifiable standing. Markets require documentation. The AI agent market has none.

📋

Liability Documentation

Who's liable for an agent's prior behavior? Without EXIT, nobody knows. EXIT creates the audit trail that enterprises, insurers, and regulators need.

🔗

Chain of Custody

Like property records for real estate or VINs for cars. EXIT creates a verifiable chain of agent transitions across platforms.

🔓

Break Lock-In

$500K customizing an agent on Platform A — that investment is hostage. EXIT documents transitions, making portability possible.

Schema

Seven fields. That's it.

A compact JSON-LD document with Ed25519 signature. Offline-verifiable. No central authority. No API dependency.

Field	Purpose	Type
id	Content-addressed hash URI	URI
subject	Who is leaving (DID)	DID URI
origin	What is being left	URI
timestamp	When departure occurred	ISO 8601
exitType	voluntary · forced · emergency · keyCompromise	Enum
status	good_standing · disputed · unverified	Enum
proof	Ed25519 cryptographic signature	DataIntegrityProof

Departure Paths

Cooperative

ALIVE→ INTENT→ SNAPSHOT→ OPEN→ FINAL→ DEPARTED

Unilateral

ALIVE→ INTENT→ SNAPSHOT→ FINAL→ DEPARTED

Emergency

ALIVE→ FINAL→ DEPARTED

Disputes modify the record. They never block departure.

For Developers

Integrate in an afternoon.

TypeScript reference implementation. One function call to create a signed, verifiable departure marker.

$ npm install cellar-door-exit

import { quickExit, quickVerify, toJSON } from "cellar-door-exit";

// Create identity + marker + sign — one call
const { marker, identity } = quickExit("did:web:platform.example");
console.log(toJSON(marker));

// Verify any marker offline
const result = quickVerify(jsonString);
console.log(result.valid); // true
    

6 Optional Modules

A: Lineage · B: State Snapshot · C: Disputes · D: Economic · E: Metadata · F: Cross-Domain

CLI Included

exit keygen · exit create --sign · exit verify · exit inspect

Standards-Aligned

W3C DIDs · W3C Verifiable Credentials · JSON-LD · Ed25519 · KERI-compatible key management

For Platforms

The infrastructure your compliance team is asking for.

SOC 2 / ISO 27001: Auditable lifecycle records for every agent transition. No more audit gaps from undocumented migrations.

Insurance underwriting: EXIT markers are to AI insurance what claims histories are to auto insurance — the data underwriters need.

Procurement compliance: Due diligence documentation for agent deployment. No CFO signs off on agents with undocumented histories.

Regulatory readiness: EU AI Act documentation requirements. NIST agent standards alignment. Be ready before it's mandated.

Non-custodial: No central registry. No single point of failure. No custodian liability for your organization.

Minimal overhead: ~335 bytes per marker. Ed25519 signing in microseconds. Zero runtime impact.

Competitive positioning: Support open agent portability standards before your competitors do.

Protocol-stack compatible: Complements A2A, MCP, AP2, Entra, SailPoint. Fills the transition gap none of them address.

FAQ

Common questions.

"Isn't this just AI rights nonsense?"

EXIT takes no position on whether agents have rights. It provides documentation infrastructure. Markets require documentation to function — that's Econ 101, not philosophy.

"Nobody's asking for this."

Nobody asked for HTTPS either. Infrastructure precedes demand. The NIST AI Agent Standards Initiative (February 2026) is actively soliciting input on agent governance. EXIT fills the transition gap.

"Why wouldn't Google or Microsoft just build this?"

They will — for their ecosystems. Platform-specific agent identity is like platform-specific email. EXIT is the SMTP: the open, interoperable layer that works between platforms.

"What if agents stay fully controlled by platforms?"

Then EXIT is harmless logging — overhead measured in bytes and milliseconds. But if agents become autonomous economic participants (which every major lab is building toward), EXIT is essential infrastructure. The asymmetry is entirely in EXIT's favor.

"Is this a transfer protocol?"

No. EXIT documents departures. It doesn't move agent weights or data. It creates the chain of custody that makes transfers auditable.