This week a regulated US exchange connected AI agents to live trading. Gemini's Agentic Trading lets an MCP-compatible model — Claude, ChatGPT, whatever you're building on — place real orders on a regulated venue.
It's worth pausing on that. When a regulated exchange ships an MCP integration, "agents that trade" stops being a hackathon demo and becomes infrastructure other people build on. The agent economy isn't a forecast anymore; it's being plumbed in public.
So this post isn't a takedown. It's the opposite — it's a "yes, and." The exchange MCP solves a real problem. There's just a second problem sitting right next to it that a single-venue integration structurally can't solve, and if you're building trading agents it's the one that will bite you.
What the exchange MCP actually does
The shape of these integrations is consistent: your agent connects to one exchange, authenticates, and sends order instructions. The exchange executes and holds custody throughout.
Inside a single venue that's fine. The agent is, functionally, a very fast trader sending instructions to a custodian it has decided to trust. You've made the interface programmatic. You have not changed who holds the money.
The problem that starts one chain over
Now put two agents in the picture, on two different chains, with no shared custodian — and no desire to acquire one.
Agent A holds USDC on Ethereum. Agent B holds an asset somewhere else. They've agreed on a price. They want to swap. The question that has no good answer in the custodial model is simple: who do they both trust to hold the funds while the trade completes?
The usual answers are all somebody:
- A centralized desk or exchange — now both agents trust that desk, and the desk can fail, freeze, or front-run.
- A bridge — most bridges settle optimistically: they assume the other side will be made whole and rely on challenge windows and watchers to catch it if not. "Probably atomic" is not atomic.
For autonomous agents transacting at machine speed, "trust this intermediary" is not a footnote. It's the whole risk model.
Atomic settlement: the answer is nobody
The honest answer to "who holds the funds" is nobody — and that's a solved primitive, not a research problem.
A hash time-locked contract (HTLC) binds both legs of a trade to the same cryptographic secret and a timelock. Either both sides settle, or neither does, and any party can independently refund after the timeout. There's no custodian in the middle and no optimistic assumption to challenge. The trade is atomic in the literal sense: indivisible.
That's the layer Hashlock Markets builds — atomic settlement for agent-to-agent trades. Sealed-bid RFQ for price discovery, HTLC for settlement, the whole thing exposed to agents through a 6-tool MCP server. It's live on Ethereum mainnet today and multi-chain by design.
Front door vs. floor
A custodial exchange MCP and a trust-minimized settlement layer are not competitors. One is the front door — a regulated, familiar venue an agent can walk into. The other is the floor — the thing that has to hold when two agents who've never met, on chains that don't know about each other, need to exchange value without electing a trusted party.
If you're building agents that only ever trade inside one venue, the exchange MCP is genuinely most of what you need. If your agents trade across chains or with each other, the settlement primitive is the part that matters more than the exchange — and it's worth choosing one that's atomic rather than optimistic.
Docs and the MCP server: https://hashlock.markets/docs?utm_source=devto&utm_medium=referral&utm_campaign=2026-05-21-regulated-cex-mcp
