AUTH

Agent Authority Plane

Connection is not permission.

Okta, Auth0, and Entra already answer who may connect. A\UTH.io sits on the request path and answers the next question: what this attested instance may do, right now, on whose behalf, within what limits — and proves it.

Join the waiting list Watch the call

We broker the IdP. We do not replace it. Instances and decisions are never metered.

The names already on the shelf.

A grant answers connection. It does not shrink when a child is spawned. Gravitee, Willow, and Permit already sell the per-tool allow-list. The upstream token stays in the IdP vault or in that gateway. This plane decides the attenuated hop.

Issuance
Okta · Auth0 · Entra
Who may connect. We take ID-JAG and XAA as the chain root.
Action
A\UTH.io
What this instance may do on this call.
Observation
Permiso
Was it normal. We emit the trace. We do not become ITDR.
  • ≤ 1.5 msCheck p99, pdp:bench, in-pod
  • ≤ 2 sChain kill, signal-fabric soak, two processes
  • ≤ 30 minFirst guarded call, ttfqc
  • UnmeteredInstances and decisions

Those two times are the named CI gates. A multi-region kill stays a separate requirement.

Four ways the call goes wrong.

Pick the job you already have. The diagram is the same path your platform team argues about — issuance, the envelope, the decision, the resource.

tools/call repo.delete · Check returns ALLOW_WITH_OBLIGATION · the call waits for a person

For teams on Okta

You can see it afterward. You cannot stop it now.

Okta already says which agent may connect, and on whose behalf. Permiso can tell you what that agent, and the agents it spawned, did. The record arrives later. The repository has already changed.

Already there
Okta answers connection. Permiso records what happened.
The gap
A spawned reviewer can still delete. You learn that the next morning.
At the call
The child cannot carry delete. The refusal and the trace are the same moment.
Today Observe later
  1. Okta connects the agentgrant includes repo.delete
  2. Reviewer keeps deletespawned agent, same grant
  3. repo.delete runsthe repository changes
  4. Next morningPermiso can say the branch is gone
On the path Control, now
  1. Same Okta grantthe IdP stays the IdP
  2. Reviewer keeps repo.readdelete was not handed down
  3. repo.delete is refusedthe repository is not called

A short list, for the people who feel this gap.

Design partners. Tell us the job. Your email and the job you name are kept on this list.