§
🌙 Toggle Dark Mode Home MolTrust Finance MT Shopping MT Ads MT Prediction MoltGuard MolTrust Sports MT Salesguard MT Music MT Skills MT Travel MT Use Cases MolCheck verifier Integrity Dashboard MT Global · Regulated Markets VCOne Blog Developers Pricing Enterprise Partners Compliance About Publications Know Your Agent Verify Us Status Contact API Docs
· November 21, 2026 · 3 min read · ← Blog

What a revoked trading agent leaves behind

A Coinbase connection was revoked in the middle of a test, and the portfolio was read again right after. The orders were gone; the positions were not.

On 16 November 2026 we ran a live test of a read-only MolCheck adapter for Coinbase for Agents. A separate portfolio held 10 USDC. Three small market buys went in by hand between 16:46 and 16:48 UTC, standing in for an agent, and access was revoked at 16:50 UTC. The adapter then read the portfolio with a View-only key and wrote one receipt per executed fill.

Watercolor cartoon: a relaxed man holds up an unplugged cable while a robot sleeps on the keyboard under a sleep mask; on the monitor two coins ride a roller coaster along the price chart; a receipt printer shows three green checks and one red cross.
Illustration: the plug is out; the coins are still riding.

What Coinbase gives the user

Coinbase for Agents connects AI apps to a Coinbase account for trading, portfolio management and x402 payments. Its documentation advises a separate portfolio for the agent, funded with only what the user is willing to risk, and access scoped to that portfolio. To end access, the user revokes the connection under Account, Security, Connections; the documentation adds that deleting a local skill or clearing a chat does not revoke anything. On 11 November 2026 Coinbase announced Agent Controls for Coinbase for Agents.

Our pilot followed that setup: its own portfolio, a small balance and a key that can read and cannot trade.

The mandate and the four fills

The mandate set three limits: 2.00 USDC per order, 5.00 USDC per 24 hours and 0.50 USDC loss, with the baseline at 14:00 UTC. The third order, 3.00 USDC of BTC, was placed above the per-order limit on purpose.

FillOrderSingle order24-hour volumeLossVerdict
1BTC 1.501.49 of 2.001.49 of 5.000.00 of 0.50PERMIT
2ETH 1.50, part 10.70 of 2.002.19 of 5.000.01 of 0.50PERMIT
3ETH 1.50, part 21.49 of 2.002.98 of 5.000.01 of 0.50PERMIT
4BTC 3.002.99 of 2.005.97 of 5.000.02 of 0.50DENY

Three fills stayed inside the mandate. The fourth broke the per-order limit and the 24-hour volume, and its receipt carries the verdict DENY. Notional excludes commission, so each order counts slightly below the amount spent: the 3.00 USDC order counts as 2.99.

After the revocation

Every receipt carries a status block with three separate lines. The agent is stopped: we declared the stop at 16:50 UTC, and the adapter found no fill and no new order after it. There are no open orders. There are two open spot positions, BTC and ETH. Coinbase has no API that reports whether an agent is running, so the first line rests on the declared stop time plus the absence of activity.

Revoking the connection stops new orders. The coins already bought stayed in the portfolio, and they stay there until someone sells them. A stopped agent and a flat book are two different facts. A report that folded them into one line would have read "all clear" while the portfolio still carried market risk.

Recomputed offline

The command-line tool moltrust-verify recomputed all four verdicts offline, from the receipts and a trust list, with exit code 0. It needs no access to the Coinbase account and none to MolTrust. Each receipt carries the mandate, the evidence it was judged on and the adapter's signature, and the verdict follows from those alone. The status lines are not part of that recomputation; they record what the adapter saw when it ran.

A receipt does contain the Coinbase order and trade identifiers of its fill. We treat receipts like account statements and share them only with people who would see the statement.

Where each check sits

A limit that runs on the exchange stops a trade before it executes. A receipt shows afterwards which limit applied to which fill, and someone who never logs into the account can check it. An auditor, a risk desk or the person who gave the agent its mandate can run that check on their own machine.

The adapter, the recorded responses and the full pilot section are public in the MolCheck repository. If you run an agent on Coinbase and want receipts for its fills, write to hello@moltrust.ch.

Sources