▸ Coinfest Asia · Discovery Spotlight

Agentic commerce is a
settlement problem

Your next customer won't browse your store. Their agent will call a tool.

mcp agentic commerce stablecoin settlement
▸ whoami

Builder first,
speaker second

Shipping payments and settlement infrastructure. Now building agentic commerce rails in production.

agentic commerce · live ex lightning labs 40× hackathon grants
Currently shipping

PaySats

An MCP server any assistant can call to quote and settle everyday purchases in IDRX through licensed partners.

mcp.paysats.exchange

▸ Thesis

Most builders treat agentic commerce as a better storefront. Agents don't browse. They need infrastructure that settles.

▸ The distribution shift

Intent moved.
Checkout didn't.

Humans used to

  • ✕Open an app, tap through screens
  • ✕Confirm with a thumb and a card
  • ✕Treat the storefront as the funnel

Agents have

  • ✓A tool schema, not a screen
  • ✓A JSON-RPC call in milliseconds
  • ✓User intent to fulfil, right now
▸ Core idea

MCP is a settlement rail
wearing a tooling costume

The reframe

Tool call = checkout

One create_order locks a quote and settles. No screen.

The gap

Everyone ships read-only

Docs and dashboards. The frontier is action servers that move value.

Why now

MCP standardized action

Every major assistant can call the same tool protocol.

▸ The UX shift

From driving UIs
to calling infrastructure

Extension era

  • ✕Headless browsers clicking web2 checkouts
  • ✕One DOM change breaks the flow
  • ✕No audit trail, manual reconciliation

Agentic infra

  • ✓Typed MCP tools: catalog, quote, order
  • ✓Settle in IDRX, licensed rupiah stablecoin
  • ✓One orderId from intent to goods
▸ Framework

Intent to goods,
one pipeline

01 · INTENT
Speak
"Restock my kitchen before the weekend."
→
02 · RAIL
MCP call
create_order · quote locked
→
03 · SETTLE
IDRX
Licensed stablecoin, on-chain receipt
→
04 · GOODS
Delivered
Merchant settled. One orderId.
▸ In production

This runs
today

Any MCP client connects to one URL, prices a cart, and settles in IDRX.

mcp.paysats.exchange settled in idrx
claude · mcp: paysats
user ▸ (voice) order me groceries for the week
agent ▸ list_merchants()
→ grocery · fresh market · food delivery
agent ▸ create_order(cart)
→ settled in IDRX · orderId: ord_7f2c
agent ▸ Delivery tomorrow. Receipt on-chain.
▸ Execution lessons

What breaks when
your payer is a model

01

Protocol is the UX

No screen. Tool order and instructions are the onboarding.

02

Lock quotes server-side

Models hallucinate amounts. Never trust the caller's math.

03

One call, whole pipeline

Quote → settle → fulfil behind one tool and one orderId.

PaySats

Build action servers,
not storefronts

The next billion economic actors won't be human. They'll call tools.

mcp.paysats.exchange coinfest.paysats.exchange thank you · terima kasih
PaySats · Coinfest Asia
01 / 10