Skip to content
AI & MCP · Confirm before writing

Nothing consequential happens without your yes

An action can run as a dry run that describes its effect and changes nothing. A consequential one will only run with the confirmation token from that dry run, for the same arguments, within five minutes.

In short

Every typed action can be called with dry_run to see its effect without changing anything. Consequential ones such as refunds, payments and stock adjustments also need a single use confirmation_token from that dry run, bound to the same arguments and valid for 300 seconds; order status changes and publishing take a token from their own preview.

The problem it solves

An assistant that misreads one number can refund the wrong amount. A confirmation that the model can invent for itself is no confirmation at all.

How it works

4 steps, start to finish

  1. 1

    Dry run

    The assistant calls the action with dry_run and gets a description of the effect.

  2. 2

    You check it

    It shows you what will happen, and nothing has changed yet.

  3. 3

    Confirm with the token

    The real call carries the confirmation_token from the dry run.

  4. 4

    Or it is refused

    A missing, reused or mismatched token gets a clear reason code.

In detail

What confirm before writing does for you

Common queries

Questions people ask

  • No. A consequential write without a valid token from a matching dry run is refused with confirmation_required.
  • The token no longer matches and the call is refused as confirmation_stale; a new dry run is needed.
  • Five minutes, and only once.

Confirm before writing · Free to start

Try confirm before writing on your own business

Set up in a couple of minutes. Your catalogue, orders and books stay yours to export.

  • Live in 2 minutes
  • Free to start
  • No credit card
The dashboard open on a laptop, a tablet and a phone