Migrating from API Keys + Manual Audit
If your agents currently authenticate with static API keys and you log actions manually, Grantex gives you verifiable permissions, automatic audit trails, and user-controlled revocation.What stays the same
- Your upstream APIs (Google Calendar, Slack, Stripe, etc.) — agents still call them
- Your users — they keep their accounts and data
- Your agent logic — business logic doesn’t change
What changes
- Auth layer: Static API keys are replaced with scoped, time-bound grant tokens
- Audit: Manual logging is replaced with tamper-evident, hash-chained audit entries
- Revocation: Instead of rotating API keys, users revoke grants through a dashboard
Step-by-step
Register as a developer
Sign up at the Grantex portal or use the SDK:
Migrating from Raw OAuth 2.0
If you already use OAuth 2.0 for agent authorization, Grantex extends the model with agent-aware grants, delegation, and built-in audit.What stays the same
- Your identity provider (Okta, Auth0, Google) — keep using it for user login
- Your users and their accounts
- The general authorize → consent → token flow pattern
What changes
- Token format: Opaque access tokens become Grantex JWTs with agent, principal, and scope claims
- Delegation: OAuth has no standard sub-delegation — Grantex tracks the full chain
- Audit: No more bolting on audit logging — it’s built into the protocol
- Revocation: Grant-level revocation cascades to all tokens (not just individual token revocation)
Step-by-step
Keep your OAuth login flow
Continue using OIDC for user authentication. Map the authenticated user to a Grantex
principalId.Replace token introspection with offline verification
Before (OAuth introspection):After (Grantex offline verification):
Further Reading
- Quickstart — Get running in 5 minutes
- Token Verification — Online and offline verification
- End-User Permissions — Principal sessions and dashboard
- Express Middleware — Drop-in middleware for Node.js APIs
- FastAPI Middleware — Drop-in middleware for Python APIs