Skip to main content

Overview

Consent bundles enable offline authorization for on-device AI agents. These endpoints manage the lifecycle of consent bundles: creation, listing, revocation, and status checks. All endpoints require a developer API key in the Authorization header unless noted otherwise.
Create a new consent bundle for offline operation. The response contains a grant token, JWKS snapshot, Ed25519 audit signing keys, and offline expiry metadata.

Request Headers

Request Body

Example Request

Response — 201 Created

Error Responses

SDK Examples


List all consent bundles for the authenticated developer.

Request Headers

Query Parameters

Example Request

Response — 200 OK

The list response does not include grantToken or offlineAuditKey.privateKey for security. Only the creation response includes these sensitive fields.

Revoke an active consent bundle. The bundle’s grant token remains cryptographically valid, but the revocation is communicated to the device at the next sync.

Path Parameters

Request Headers

Example Request

Response — 200 OK

Error Responses


Check Revocation Status

Check whether a consent bundle has been revoked. This endpoint is useful for devices that want to verify bundle validity without performing a full sync.

Path Parameters

Request Headers

Example Request

Response — 200 OK

Or if revoked:

Error Responses


Refresh an active consent bundle to extend its offline expiry, update the JWKS snapshot, and rotate the audit signing keys.

Path Parameters

Request Headers

Example Request

Response — 200 OK

Returns a full ConsentBundle object (same schema as the create response) with updated fields.

Error Responses


Rate Limits

Last modified on May 23, 2026