Guide

Confirm fills in the broker, not chat

Treat the broker or wallet UI as the source of truth for fills and balances. Chat summaries and agent claims can lag, hallucinate, or miss partials — confirm there before the next place or before you raise the sleeve. Pair it with never skip review before place, receipt log after the session, paper before live, fund the session ceiling, and session time-box.

By Agent Lane Editorial · Page dated 27 September 2026

Answer first

After a live place, pay, or move — and before the next place or before you raise or refill the sleeve — open the broker or wallet UI you control and confirm fills, partials, rejects, and spendable balance there. Do not treat the chat transcript or an agent “filled” claim as settlement. Agents summarize; venues settle. Agent Lane publishes the checklist. We do not place trades, hold wallets, or run your agents.

What this page is

A short operator guide for the venue-truth step on the shield — the habit siblings imply when they say write what ran and do not raise on a fuzzy picture. Pair it with never skip review before place, review before place, receipt log after the session, paper before live, fund the session ceiling, session time-box, rotate before you raise the balance, revoke before you debug, and agent spend caps.

We are a publisher, not a trading desk. Product screens change; confirm labels on the official page before you put money in. We do not invent a broker fill screen or API for readers.

Why trusting chat as the fill record is the failure mode

• Lag. Chat can report “filled” before the venue shows it — or after a cancel already hit.
• Partials and rejects. An agent summary often collapses a partial, a rest, or a reject into one confident line.
• Hallucinated success. Models invent clean fills when a connector timed out, a preview failed, or the tool returned an error the bot soft-pedaled.
• Wrong balance → wrong raise. Raising the sleeve or placing again on a chat balance skips the ceiling you meant to keep — see fund the session ceiling.

What “confirm fills in the broker, not chat” means

• Venue UI first. Orders, activity, positions, or balance views the official product exposes — not the chat scrollback.
• Fill state. Filled, rejected, still open, or partial — quantity/notional and asset matched to what you approved.
• Balance left. Spendable cash in the sleeve vs the session ceiling before any raise or refill.
• Then the receipt. Write confirmed fields into your receipt log before empty/raise.
• Gate stays on. No standing skip — never skip review before place.

Where it sits in the shield stack

1. Dedicated agent wallet — money the bot can reach; long-term holdings stay outside.
2. Spend caps — session and daily maxes you write and enforce.
3. Fund the session ceiling — empty or park excess, then put in only that ceiling for this run.
4. Session time-box — hard end time for the live window.
5. Review before place / never skip — human gate stays on each place.
6. Confirm fills in the broker, not chat — venue UI is source of truth after the click.
7. Receipt log after the session — write what the venue confirmed before empty/raise.
8. Revoke before you debug — kill-and-isolate when venue and chat disagree badly or something misfires.

Healthy run uses gate + venue truth + receipt. Skip the venue check and you can raise or place again on a hallucinated fill.

How to confirm fills in the broker

1. Keep review before place on. Amount, destination, asset, and venue shown before any place, pay, or signature. No standing “just place it” — see never skip review.
2. After place, open the venue UI. Use the official broker or wallet UI for that sleeve — orders, activity, positions, or balance. Do not invent a product screen; use what you already use for that account.
3. Confirm fill state. Filled vs rejected vs open vs partial; quantity or notional; asset or symbol; fees if the UI shows them. Match to what you approved at the gate.
4. Confirm balance left. Read spendable balance against your session ceiling before any raise or refill. Overnight or idle still follows empty the sleeve overnight.
5. Write the receipt log. Copy confirmed fields into your receipt log after the session before empty/raise.
6. Only then place again or raise. Next place stays inside the session time-box. Raise/refill only after rotate before you raise the balance when credentials need a pass. Chat/venue mismatch or a bad fill: revoke before you debug — disconnect → lock → empty sleeve → revoke or rotate — then dig. Prefer paper before live until the pipe proves clean.

Practical checklist

• Venue before chat. Broker/wallet UI wins; agent summaries do not settle.
• Partials count. A half-fill is not “done” — confirm rest or cancel in the UI.
• Balance before raise. Never top up on a chat-reported balance.
• Receipt from venue fields. Log what the UI showed, not what the bot claimed.
• Shared-box pass. Confirm in the same profile that owns the sleeve — see separate browser profile and shared-box.

Brokerage path: Shield brokerage spend. On-chain pay: Shield crypto spend and x402 buyer basics.

What Agent Lane does not do here

• We do not place trades, preview your orders, or babysit your agents.
• We do not hold your funds, run a hot wallet, or settle payments.
• We do not publish “trust the chat fill” as a workflow or invent a broker fill product UI.
• We do not invent broker APIs or product click-paths for order history.

Related guides

• No place while unconfirmed fill
• Write max loss before entry
• Confirm symbol before place
• Reject duplicate place same thesis
• No chase after partial fill
• Reject agent place without a fresh quote
• Confirm buying power before place
• Never skip review before place
• Confirm cancel in the broker, not chat
• Receipt log after the session
• Paper before live
• Fund the session ceiling
• Session time-box
• Review before place
• Rotate before you raise the balance
• Revoke before you debug
• Agent spend caps
• Dedicated agent wallet
• Empty the sleeve overnight
• One venue, one agent session
• Shield brokerage spend
• Shield crypto spend
• x402 buyer basics
• Write invalidation before entry
• Reject duplicate place same thesis
• Confirm symbol before place
• No scale-in without GO
• Flatten all before connector revoke
• One order per idea until fill
• No place while unconfirmed fill
• Shared-box and connector checklist
• Revoke connectors when idle
• Dry run before first live place
• Two-person rule for large places
• Log session end checklist
• More on Resources

FAQ

What does confirm fills in the broker, not chat mean?

It means: after a place, pay, or move — and before the next place or before you raise or refill the sleeve — open the broker or wallet UI you control and confirm fills, partials, and balances there. Chat summaries and agent claims can lag, miss a partial, or invent a fill. The venue UI is the source of truth for this checklist.

Why is trusting chat as the fill record the failure mode?

Agents summarize; they do not settle. A chat line can lag the venue, skip a partial fill, round a notional, or hallucinate a success after a reject. If you raise the sleeve or place again on that summary, blast radius grows on a wrong picture.

How is this different from review-before-place or receipt-log-after-session?

Review before place is the human gate before the click. Receipt log after the session is the operator note you write after the run. Confirm fills in the broker is the venue-truth step — look at the broker or wallet UI for what actually filled before you trust chat, raise the sleeve, or place again. Use all three.

Does this replace paper-before-live or fund-session-ceiling?

No. Paper before live proves the pipe without live money. Fund the session ceiling bounds cash in the sleeve. Confirm fills is the truth check against the venue after a live place. You still need the full stack.

What should I confirm in the broker or wallet UI?

Filled vs rejected vs still open; partial vs full; quantity or notional; asset or symbol; destination or account; fees if shown; and the spendable balance left in the sleeve. Match those fields to what you approved at review before place.

Do I invent a broker product screen?

No. Use the official broker or wallet UI you already use for that account — orders, activity, positions, or balance views the product exposes. Agent Lane does not invent product menus, click-paths, or API claims for fills.

Where do I apply this next?

Gate: never skip review before place. After the run: receipt log after the session. Dry prove: paper before live. Cash: fund the session ceiling. Clock: session time-box. Incident: revoke before you debug. Agent Lane publishes the checklist; we do not place trades or hold wallets.

Next steps

Before an agent touches real money, review every order before it is placed, shield your brokerage account, and map the trading-agent options. Or browse all Agent Lane guides.