Solutions · Autonomous agents

Agents need authority, not just intelligence.

A model can reason. It cannot hold an identity, reach a private service or settle a payment.

The problem

You are already asking these questions.

Each answer lives in a different system. None belongs to the agent.

How does an agent authenticate itself?
Who owns it?
What happens when it spends money?
How do you restrict what it is allowed to do?
How do you prove afterwards what it actually did?
How does it pay another machine without a human in the loop?

The principle

Identity belongs to the entity that controls the key.

An API key names a caller. An agent identity is held by the agent, with a human supervisor on record.

What an agent identity carriesAn agent identity drawn as a spine with four branches. At the top, a human identity, drawn with a dashed outline: identity verification backends are not connected, so the supervisor relationship here is a cryptographic link between keys rather than an externally attested legal identity. A link labelled supervises, recorded at the network layer, runs down from it to the agent identity, which is drawn solid. Four branches hang off the agent identity. A wallet: signed transfers from an address the agent holds. A delegation, drawn larger than the others because it is the part that does not exist elsewhere: it contains a bracketed region holding its four bounds - scope, meaning which actions; sub-delegation, meaning whether it can be passed on; duration, meaning how long it holds; and expiry, meaning when it lapses - and the whole delegation is revocable by the supervisor at any time. A UNP address: reachable without publishing the host machine. And a record: state either party can check independently.

Architecture

Five accounts, or one identity.

Today

API key in a secrets manageridentity
Cloud IAM roleauthority
Payment provider accountpayment
Cloud compute accountexecution
Provider-side logaudit

On UniNet

Agent identityhuman supervisor recorded
Delegated authorityscoped · revocable
Discover · authorize · paynetwork primitives
Isolated containerresource limits
Result to the agent identityreturned over UNP
Recorded statecheckable by either party

Evidence

What you need, and what the network provides.

What you need	UniNet primitive	Status
Agent identity	Its own identity type, distinct from a personal one.	Ungraded
Human accountability	A supervisor link between keys. Verification is not connected.	Not implemented
Wallet and payment	Signed transfers and sub-wallets. Pays another identity with no approval step.	Available
Delegated authority	Scoped. Revocation cascades to re-delegated rights.	Available
Service discovery	CPU, memory and storage across nodes, reserved atomically.	Available
Network privacy	An address decoupled from the machine, reachable across validators over a circuit of one to three relays. Not an anonymity guarantee.	Available
Execution	Container-level isolation only. No hardware-backed confidential compute.	Available
Persistent state	Storage under the agent’s own identity.	Available
Cross-chain activity	Ethereum bridge verification. No asset has crossed yet.	In development
Auditability	Recorded as network state, not by the audited party alone.	Ungraded

Ungraded means described, not signed off for production. Check before you design around it

Reference design

An agent acquires compute it had no account for.

No human creates an account, approves a call or releases the payment.

01Create identityUngraded
02Receive delegated authorityUngraded
03Search available computeIn development
04Evaluate providersIn development
05Select a providerIn development
06Reserve computeIn development
07Send the workload privatelyIn development
08Execute in isolationIn development
09Receive the resultUngraded
10Verify the transactionUngraded
11Pay the providerUngraded
12Record the interactionUngraded

Not running end to end today; steps 03–08 depend on multi-node compute orchestration. See what runs today

Possibility

What you can build against this.

An agent with its own key and wallet, paying another identity with no human approval step.

Contact What works today Run a node