Interactive Playground
Walk through the Grantex sandbox authorization flow in your browser. Start creates a fresh sandbox account; no existing key is needed.
The default demo creates a fresh sandbox key. To use your own, select the option above and enter a sandbox key from the Dashboard. Never enter a live or production key here.
The auth service endpoint. Your key will be sent to this URL; use HTTPS, or localhost for local development.
Register a demo agent that will request permissions on behalf of a user. This creates a cryptographic identity (DID) for the agent.
POST /v1/agents
Response
Ask a user for permission. In sandbox mode, this auto-approves and returns an authorization code immediately — no consent page needed.
POST /v1/authorize
Response
Exchange the authorization code for a signed RS256 JWT grant token. This is the credential your agent presents to any service.
POST /v1/token
Response
Decode JWT Claims
Verify the grant token online. Production services can validate locally using keys retrieved from JWKS; fetching or refreshing those keys may require a network call.
POST /v1/tokens/verify
Response
Exchange the single-use refresh token for a new grant token while the grant is active. A lost response can be recovered for 300 seconds; refresh does not extend grant expiry.
POST /v1/token/refresh
Response
Revoke the grant and its descendants centrally. Services that verify JWTs locally must also consult current revocation state or use short token lifetimes.
DELETE /v1/grants/:id
Response
Try verifying the same token again. It should now return
valid: false — proving that revocation is effective.POST /v1/tokens/verify
Response