Skip to main content
Pay3 provides two revocation endpoints so you can cut off an AI assistant’s spending access immediately — whether you need to retire a single session or perform an emergency shutdown of all active sessions at once. Revoking a session invalidates its MCP auth token and prevents any further transactions from being submitted under it. Any transactions that are already in the SIGNING or SUBMITTING state at the moment of revocation may still complete.

​
Revoke a single session

Remove access for one specific AI session by its ID. Use this when rotating session credentials, decommissioning a particular AI client, or responding to a suspected compromise of a single token.

​
Endpoint

​
Authentication

​
Path parameters

​
string
required
The UUID of the AI session to revoke.

​
Response

Returns HTTP 204 No Content on success — no response body is sent.

​
Error responses

​
Example request

​
Revoke all sessions

Immediately revoke every active AI session on your account. This is an emergency control designed for situations where you suspect a credentials leak, want to perform a full security reset, or are shutting down all AI-driven activity.

​
Endpoint

​
Authentication

​
Request body

No request body is required.

​
Response fields

​
number
required
The number of active sessions that were revoked by this call. Returns 0 if no active sessions existed at the time of the request.

​
Example request

​
Example response

Revoke-all is irreversible. All active AI sessions will be disconnected immediately and their MCP auth tokens permanently invalidated. Every AI assistant currently using Pay3 — Cursor, Claude, ChatGPT, or any other client — will lose spending access at once. You will need to create new sessions and re-configure each client to restore access.
Revoked sessions remain visible in GET /api/ai-sessions with a status of REVOKED, so your audit history is preserved.