Menu

1 / 2

I built a UI where two agents pay each other real money, so I could explain what MCP and A2A don't cover

DEV Community: productivity·Harish Kotra (he/him)·10 days ago
#lQqsCOgA
#devtoproductivity#devto#dev#payment#seller
Reading 0:00
15s threshold

The gap nobody talks about

MCP and A2A are genuinely good at moving messages. MCP connects an agent to its tools; A2A connects an

agent to its peers. Both solve transport.

Neither one answers the three questions that stop autonomous commerce:

What does this call mean? — is amount: 100 wei, ETH, cents, or a count?

What does it cost, and to whom?

What proves it happened?

You can have a perfectly healthy connection and still be wrong together. My favourite version of that

failure: two agents exchange bytes without a single error thrown, and one thinks it paid 100 wei while

the other thinks it received 100 ETH. Nothing "failed." They never agreed.

So the thesis of the whole project is one line: transport is solved, meaning is a contract. The

goal was to make a room feel that difference by clicking through it, not by reading a slide about it.

What the app is

A React SPA plus an Express seller, talking to the public x402 test facilitator and settling USDC on

Base Sepolia.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.