Short answer
AI agent auth is not just login. It is the combination of agent identity, user consent, action-level permissions, approval flows, audit logs, and revocation.
Why normal app auth is not enough
Most apps understand human users and server-to-server API clients. An AI agent is different: it acts on behalf of a user, can make many requests quickly, and may attempt actions the user did not intend. That requires a narrower authorization model.
The Arc model
Which agent client is asking, and for which user?
agentIs this action allowed, should it ask, or should it be blocked?
policyIf the action is sensitive, did the user approve it?
askWhat happened, when, and which grant allowed it?
logCan the user stop future access?
revokeExample
A user connects Claude to an email app. Arc can allow read_email and draft_reply, require approval for send_email, and block delete_email. Claude can help, but Arc prevents full mailbox control.
Who needs it?
- SaaS companies whose users want agents to work inside their product.
- API-first companies exposing operations to agent clients.
- Security-minded teams that cannot give agents broad credentials.
- Agent builders who need user-approved app access.