HomeUse cases › How to revoke an AI agent’s access
Use case

How to revoke an AI agent’s access

Kill a compromised or misbehaving agent's authority in one call — and have it cascade to every sub-agent it delegated to.

Why key rotation is the wrong tool

If an agent holds an API key and it leaks, your only lever is rotating the key — which breaks every other legitimate user of that key and takes a redeploy. A warrant is revocable on its own: revoke it by id and it, plus everything derived from it, stops verifying immediately.

Revoke by root id

// gateway: POST /revoke { jti }  (or /t/revoke with your API key)
await client.revoke(rootJti); // every warrant descended from this jti now fails

Revocation cascades: because each delegated warrant is cryptographically derived from its parent's id, revoking the root invalidates the entire tree of sub-agents in one action.

Combine with short expiries

Belt and suspenders: give warrants a short expires so stale authority dies on its own, and keep revocation for the moment you need it now.

Frequently asked

What is Liceat?

Liceat is permission infrastructure for AI agents. You issue a warrant — a scoped, spend-capped, revocable token — that grants an agent narrow authority; the agent presents it at the point of action; Liceat enforces it (scope, spend, rate, holder-binding, revocation) and records every decision in a tamper-evident log. It is open source with a zero-dependency SDK for TypeScript and Python.

Is it free?

The SDK and self-hosted gateway are free and open source. The hosted gateway at liceat.com gives 10,000 free decisions with no card, then meters at fractions of a cent per decision — payable by card or USDC.

Give your agents permission, not your keys.

Free to self-host. 10,000 free decisions on the hosted gateway — no card.

Get an API key Read the docs