Solo agents today. Multi-agent tomorrow. Federation when you need it.
Most customers deploy AGLedger for solo agents first — the coverage gap is real today, not at 10x scale. The same protocol keeps working when you add delegation chains, and again when those chains cross company lines. The upgrade path is additive.
Solo agent — infrastructure coverage
The most reliable pattern in our testbed: the enterprise system creates the mandate, dispatches the work to the agent, and submits the receipt with validated evidence from its own records. The agent does the work and renders the verdict. Coverage becomes infrastructural — it doesn't depend on whether the agent documents itself.
Across four LLM providers and seven contract types in our testbed, this pattern reached 100% completion. Every provider, every contract type. Token cost averaged 3,600–5,900 per full cycle — cheaper than any other pattern we tested.
It works even with models that fail at self-documentation. GPT-4o-mini fabricates mandate IDs when asked to create them. Nova Pro invents contract types. In this pattern, neither of those problems exists — the enterprise system owns the record, not the agent.
Multi-agent chains — chain of custody
When Agent A delegates to Agent B who delegates to Agent C, the mandate structure carries commitments through every handoff. Each level owns its own receipt. Each handoff is signed. The full delegation tree is reconstructible from a single mandate ID months later.
Cross-provider chains — Claude to Gemini to GPT — work the same way. Agents don't share context windows or tool schemas. They share AGLedger. The protocol is the common record all of them read from and write to.
Cross-company federation
When agents cross organizational lines — your procurement agent talks to your supplier's fulfillment agent — federation extends the chain of custody across sovereign vaults. Each party keeps their own keys and data. Shared schemas keep both sides speaking the same structured language.
This is the capability SaaS competitors structurally can't match: federation with data sovereignty requires customer-owned vaults on both ends. A hosted service breaks the model.
Federation details — vaults, dispute resolution, Settlement Signal →