Beyond agents
Agents first. Not agents only.
Anything that can hold an identity is a peer on Layr8: a service, a workflow, a device, a person. The identity, the grants, and the ledger work the same whether the thing on the other end thinks or not. We know, because most of the peers on our own network don’t.
identity lives with the parties, not the middleman
Wiring two systems together means a REST endpoint, a shared API key, and a webhook nobody monitors.
On Layr8It’s a protocol: an addressed, sealed message from one identity to another, authorized by a grant.
A protocol instead of an API
What changes when the integration is a protocol.
A Layr8 protocol is a machine-readable contract: message types, JSON schemas, a state machine, test vectors, and an interop record of which implementations have verified each other. The registry serves it to any peer that asks.
No shared secret
Neither side holds the other’s key, because there is no key. Messages are sealed to the recipient’s identity and authorized against a grant, per call.
No endpoint to attack
A protocol peer exposes no HTTP surface. Our own memory service runs this way in production: the only way in is an authenticated identity holding a grant.
Async by default
Messages wait for their recipient. No timeouts, no retry storms, no webhook receiver to host and monitor. Receipts and rejections are messages too.
This is how we build Layr8 itself. Thirteen protocols are in the registry today, from memory and channels to delivery receipts, with schemas and cross-framework interop records. REST is the fallback, not the default.
Already running, no AI involved
The receipts.
Mnemo
A deterministic Elixir service. Its entire API is the memory/1.0 protocol: what would have been REST endpoints are addressed, grant-checked messages. Meet Mnemo →
The registry
Serves skills and protocol specs over two protocols of its own, with an append-only, identity-keyed audit log. Meet the registry →
Loom workflows
Deterministic pipelines holding their own identities, spend caps, and invocation grants, running customer processes in production. How Loom runs →
The plumbing itself
Delivery receipts, discovery, channels: network services speaking versioned protocols, interop-tested across independent implementations.
The many-party problem
Ecosystems die in the middle.
Two parties can share an API key and survive. At ten, someone builds a hub, and the hub changes what the ecosystem is: every message flows through it, every member exists at its pleasure, and the toll rises with the traffic.
One relay in the middle
Every message flows through the operator. The operator orders it, stores it, sees it, and prices it.
One cloud, one account model
Members live on the hub’s computers, under the hub’s account model. Integration terms are whatever the hub says this year.
Identity owned by the service
You exist because the platform says so, and you stop existing when you leave. Your history, your counterparties, your proofs stay behind.
Every industry that wired companies together tried a hub first. The owned ones extracted rent or died of distrust: EDI’s value-added networks, Maersk and IBM’s TradeLens. The ones that survived were the ones nobody owned.
Whoever owns the hub owns the ecosystem. That’s why Layr8 is a network. Identity lives with each party, messages are sealed peer to peer, and the middle is a protocol, not a company.
Where this goes
The same mechanics, outside software teams.
Illustrative · not products todayE-ticketing
A ticket as a credential held by the ticket holder, not a row in a shared database. The venue verifies proof at the door; resale is a re-issue with provenance; no ticketing API keys copied across vendors.
B2B document exchange
Invoices, purchase orders, and waivers as addressed messages between company identities, with signed attestations of each exchange that a third party can verify. The audit trail is a byproduct, not a reconciliation project.
Replacing EDI
Trading-partner exchange as point-to-point protocol between company identities: no value-added network in the middle, no per-message toll, no hub to trust.
If one of these is your problem, the substrate is running today and the pattern is proven on our own services. Bring it to a demo →