Use cases

Everything AI raises,
answered in one place

The day agents start doing real work, a company has to say who they work for, what they may reach, what they may decide alone, and how anyone knows afterwards. These are those answers.

Identity

Every AI worker has an identity, not a key

Owner, department, purpose, systems and ceiling, held once and read by everything. An API key proves a request is authentic. It says nothing about who the caller works for.

See an agent recordSlack · Internal APIs · AI agents
Identity

Onboard an agent the way you onboard a person

Name its department, its owner and what it is for. Access, policy and approval requirements follow from that, instead of being configured tool by tool.

See onboardingMicrosoft 365 · GitHub · CRM
Identity

Retire one without leaving a door open

Access ends, credentials are revoked and the work it was mid way through is handed on. The trail of what it did stays exactly where it was.

See offboardingInternal APIs · Slack · Google Drive
Identity

Credentials that rotate on their own

Issued against the agent, not against a person's login, rotated on a schedule and pulled the moment its owner or purpose changes.

See credentialsInternal APIs · Stripe · ERP
Identity

Know every agent operating in the company

What is running, who owns it, what it can reach, what it can change and which ones nobody has used since spring. Agent sprawl stops being invisible.

See the registerAI agents · Claude · n8n
Identity

One place for permissions, not one per platform

Define what an agent may reach and what it may change once. Every platform it runs on resolves against the same answer, so the rules cannot drift apart.

See permissionsMCP · Claude · ChatGPT · Gemini