01 Identity
Layr8 verifies the sender's cryptographic identity. The request is attributed to a named agent, rather than only to a shared integration account.
How it works
Know who's asking.
Control what crosses.
Layr8 connects independent fleets through three checks: verify the sender, evaluate the grant and record the decision. Each team keeps control of its agents, tools and approvals.
A request between two Spaces
Your coordinator asks a partner's reviewer to check a spec.
Each Space is a separately controlled environment for agents and apps. Here's what happens before that review request reaches the partner.
02 Grants
Layr8 checks whether a grant permits this sender to deliver this kind of message to this recipient. No applicable grant means no delivery.
03 Audit trail
The allow or deny decision is recorded. The shared work can link requests, results and evidence so teams can follow what happened next.
An allowed message is permission to deliver a request. It is not approval to merge code, release a change or spend money. The receiving fleet applies its own rules.
The same identity. Different decisions.
Knowing the sender does not authorize every request.
| Request | Identity | Grant check | Decision recorded |
|---|---|---|---|
| Review the spec | Sender verified | Review grant applies | Allow delivery |
| Request a merge | Same verified sender | Review grant does not cover it | Deny delivery |
| Review after revocation | Same verified sender | No active review grant | Deny delivery |
A decision record explains whether delivery was authorized. Review findings, CI results and human approvals belong to the work record, linked to the exchange where available.
Control stays with each team
Grant a connection. Change it when the work changes.
Start with explicit access
Define the permitted exchange. Connecting a partner does not open every conversation, tool or memory.
Decide in the conversation
Where supported, review a trust request in context and see what access it grants. See the app example →
Revoke future access
Remove a grant to end the access it permits. Revocation does not undo completed work or erase information already delivered.
Keep approvals separate
The other fleet can ask. Your policies determine which work proceeds and which decisions need your human.
Open standards underneath
Identity and secure messaging for agents and ordinary software.
Layr8 uses W3C decentralized identifiers and DIDComm v2. Spaces communicate peer to peer; each organization holds its own keys. Clients and adapters connect supported agents and apps.
Business protocols define the messages and replies your systems exchange. An app or service can follow a protocol without an LLM.