Use cases
8 real-world agent commerce scenarios, each ending in a verdict and signed evidence. Grounded in incidents that actually happened in 2026.
Band 01
Screen agent checkouts, protect inventory, and keep evidence for the disputes that follow.
Scenario 1
BLOCKSituation
An agent checks out with valid-looking credentials. Its principal, the person or organization that owns it, never authorized the payment.
What FLINT returns
BLOCK, with the signed record that becomes your chargeback evidence.
Scenario 2
REVIEW + BLOCKSituation
400 throwaway agents share 1 operator. They cart inventory at machine speed.
What FLINT returns
Coordinated behavior is detected across the network, moving the swarm to REVIEW and BLOCK before stock is gone.
Scenario 3
ALLOWSituation
A legitimate shopping agent reaches checkout. Your fraud stack would have refused it.
What FLINT returns
ALLOW with a trust score, and the sale you would have lost.
Band 02
Check the buyer or counterparty before you deliver value, then attach the signed decision to the transaction.
Scenario 4
REVIEWSituation
An x402 buyer you have never seen requests your API. Verify it before you fulfill.
What FLINT returns
REVIEW until the buyer's authority is clear, with a signed record attached to the sale.
Scenario 5
STEP-UPSituation
Your agent is ready to pay a counterparty it has never met. 1 call checks the counterparty and records your agent's authority before it spends.
What FLINT returns
STEP-UP requests more proof before payment, while preserving the authority check in a signed record.
Scenario 6
BLOCKSituation
A compromised agent starts touching services and counterparties outside its mandate. It follows the shape of the July 2026 OpenAI rogue-agent incident.
What FLINT returns
Authority is checked at each boundary, so the pivot gets BLOCK, not a pass.
Band 03
See who owns every agent, what it could do, what it did, and the signed evidence behind each outcome.
Scenario 7
EVIDENCE READYSituation
The examiner asks for every agent transaction in the organization. The owner, mandate, and outcome are already signed and filed.
What FLINT returns
A rendered evidence trail shows each agent, owner, mandate, decision, and signed record.
Scenario 8
BLOCKSituation
An agent's spending authority is escalated without its owner. The unauthorized change appears before the agent can use it.
What FLINT returns
Sentinel alerts, the freeze lands, and the authority change is logged.
Sentinel response sequence
Sentinel alert
Spending authority changed without owner approval.
Freeze landed
The agent cannot transact while the change is reviewed.
Change logged
The previous mandate, attempted change, and response are signed.
Interactive runner
These scenarios use the live runner already built into this page. The other 5 show static signed evidence without pretending to run a workflow.
Scenario phase: waiting
Store checkout
An agent checks out with valid-looking credentials. Its principal, the person or organization that owns it, never authorized the payment.
Event
Standard check
FLINT screen
Waiting for run.
FLINT verdict
Verdict
PENDING
Signed evidence
Waiting for run.
Valid payment details do not prove that the agent had permission to use them.
Why this matters
FLINT checks authority before the merchant ships, then signs what it saw and why it blocked the sale.
From the casebook
How a legitimate agent can inherit dangerous authority through a chain of trusted tools.
Read the brief →Why machine-speed fulfillment needs a verification decision before the resource is released.
Read the brief →A plain-language guide to connecting an agent, its owner, and its authority to spend.
Read the brief →