OAuth for AI Agents

OAuth lets a user grant an application scoped, revocable access without sharing a password — which maps well onto giving an agent bounded authority. For agents it is a real improvement over shared API keys: scoped tokens, consent, revocation. What it does not supply on its own is a verifiable chain back to the accountable human and attenuating delegation between agents, which agent authority needs — so OAuth is a strong base to extend, not the whole answer.

Gives

Scoped, consented, revocable access

Better than

Shared API keys

Lacks

Verifiable delegation chain

Role

A base to extend, not the whole answer

Scopes are a start

OAuth’s scoped grant and consent step already encode "this app may do these things on my behalf" — the shape agent authority wants. The gap for agents is attenuation and verification: an agent delegating to another agent should carry only a subset of its own authority, and a service should be able to verify the whole chain back to a human. OAuth is where many agent-auth designs sensibly begin.

Questions

Can agents use OAuth today?

Yes. OAuth-style scoped tokens give an agent bounded, revocable access, which is far better than a shared key. Agent systems extend it with verifiable, attenuating delegation.

What does OAuth not cover for agents?

A verifiable chain of delegation back to an accountable human, and attenuation when one agent delegates to another — the invariants agent authority needs.