Know who acted, even after delegation.
Autos gives every agent a persistent, unforgeable identity, however many hops from the human who started the task. It carries that identity from the initiating person through agents and tools, so handoffs do not erase attribution. Agents only ever hold an API key; signing keys are held by a Sentinel gateway and signing happens off-device.
Delegate as far as you like.
Add hops to the chain, then switch to service accounts and watch where the person who started it drops out of the record.
A purchase, handed down the chain
Each hop is an agent handing work to another. The question at the end is the one an auditor asks: who did this?
Illustrative
Handoffs should not erase who acted.
Service accounts and shared keys
Attribution stops at the first handoff
- The account acts, so the person behind it is not in the record.
- Keys sit with the agent, so compromising the agent compromises the key.
- Every delegation adds a hop nobody can trace back.
- Identity for agents is a parallel system to identity for people.
Autos
One identity, however many hops
- A persistent identity carried from the initiating human through agents and tools.
- Agents only ever hold an API key. Signing happens off-device.
- Delegation adds hops without adding anonymity.
- Human identities already in your directory are mapped in, not duplicated.
Know who acted, even after delegation.
Attribution that survives handoffs
An action six agents down the chain is still attributable to the person who started the task.
Nothing to sign with on the agent
Signing keys are held by a Sentinel gateway, not by the agent, so compromising an agent does not expose the key.
Extends the IAM you have
People already managed in your identity provider are mapped in, so agentic identity is an extension, not a second directory.
Identity, delegation and keys, answered.
What identity and security teams ask before agents start acting on someone's behalf.
What is Autos?
Autos is the identity layer of the Weilliptic platform. It gives every agent a persistent, unforgeable identity, however many hops it sits from the person who started the task, so handoffs between agents and tools do not erase attribution.
Why not use service accounts for agents?
A service account replaces the identity of whoever is acting with a shared credential, so after the first handoff the record shows the account rather than the person responsible. Autos carries one identity from the initiating human through every agent and tool in the chain.
Does an agent hold its own signing key?
No. Agents only ever hold an API key. Signing keys are held by a Sentinel gateway and signing happens off-device, so compromising an agent does not expose the signing key.
What happens to identity when an agent delegates to another agent?
It is carried through. Each hop acts for the same identity root, so an action taken three or six agents down the chain is still attributable to the person who started the task.
Does Autos replace our existing identity provider?
No. Human identities already managed in Entra ID are mapped in bidirectionally, so agentic identity extends your existing IAM rather than replacing it.
How does Autos relate to Writ?
Autos answers who is acting. Writ answers what they are allowed to do. Writ issues each grant to an identity Autos keeps intact, which is what makes an authorization traceable back to a person.