Mandate Inspectorby Blisk
blisk.xyz →

What is this agent allowed to do?

AI agents pay for things by presenting signed payloads. Paste one, or just click a sample below, and get the answer in plain language.

1 who authorized this2 what exactly they authorized3 is any of it enforced, or just claimed
enter ↵ runs
New here? What these formats are and where you would meet them
AP2 mandate

Google's Agent Payments Protocol. A signed JSON mandate an agent carries to prove a user authorized a purchase. You'd receive one from an AP2-speaking agent at checkout.

x402 payment header

The HTTP 402 payment flow used for machine-to-machine payments. This block is what a server returns and what the client signs back. You'd see it in network logs of an agent paying per call.

ACP checkout

Agentic Commerce Protocol: the checkout session an AI assistant creates when buying from a merchant, with a shared payment token from the platform. Merchants see these on agentic orders.

Visa agent credential

Visa Intelligent Commerce: a tokenized payment credential issued to a registered AI agent, with network-side spend controls. Issuers and agent platforms handle these.

BLISK authorization

A commitment signed under a BLISK mandate: the institution's policy compiled into the signing key itself, plus a public attestation. Counterparties receive this with any commitment.

Gnosis Safe

A widely used multisig treasury contract on Ethereum. Paste its 0x address and everything about its policy is on chain for anyone to read.

BLISK-secured account

A smart account controlled by a BLISK-compiled key. On chain it looks like a single key; the policy is provable through the public registry without being exposed.

Agent key (registered)

A bare public key or DID an agent identifies with. Alone it proves nothing; the question is whether a verifiable authorization exists for it anywhere.

Agent key (unknown)

The other outcome: a key with no verifiable authorization anywhere. This is what most agent keys look like today.