Confirmation cards
The confirmation card is taker’s central safety object. Every mutating action produces one, and every number on it is computed server-side from live market data — never by the language model.
What the card shows
Section titled “What the card shows”| Row | Meaning |
|---|---|
| Action | What will happen, in words: “Open 5x long ETH” |
| Size | Position size in the base asset (e.g. 1.0582 ETH) |
| Order value | Notional in USD |
| Est. entry | The price the order is expected to fill at |
| Liquidation | Where the position would be liquidated, or ”—” |
| Margin required | What this order locks up as collateral |
| Fee | All-in cost: venue fee plus builder fee, itemised |
| Max slippage | How far from the estimate the fill may land |
A dash means not computable, never zero. Under cross margin, a liquidation price depends on your whole account, so a single position’s number would be a fiction — taker shows a dash rather than inventing one.
Why a card can expire
Section titled “Why a card can expire”A card is a quote at a moment. Prices move, so cards carry a short lifetime (about 90 seconds). Confirming an expired card does not execute at a stale price — it is refused, and you ask for a fresh one.
If the market moves materially between the card being drawn and you confirming, the order is likewise refused rather than filled somewhere you did not agree to.
Reading a close card
Section titled “Reading a close card”Closing a long is a sell. taker colours the card by the side of the order that will actually cross the book, not by the position you hold, so a close of a long renders in the sell colour. Green means buy everywhere in the product, including here.
When there is no card
Section titled “When there is no card”With 1-click enabled, orders execute without a card. A toast confirms what happened — size, price, notional — and the position updates immediately. Every server-side control still runs; what is removed is the click, not a check.
The one exception that always requires a click: an order proposed in a turn where the assistant used web search. Fetched web content is untrusted text, and the human click is the control between it and your account.