← Back to dashboard
10 Real-World Scene

Café Walk-by

Saturday morning. Patty is walking through Siolim when her phone vibrates softly: “Work-In-Progress is 40 meters ahead. Your usual flat white?” She nods. By the time she reaches the counter, the barista slides her cup across. No queue. No wallet. No app. Her agent discovered the café’s .well-known/agent-payment endpoint, read her preferences, placed the order over x402, and paid 4.50 USDC — all before she finished crossing the street.

Proximity-triggered, fully autonomous commerce. The moment your agent knows you’re nearby, the transaction is already done.

Play this scene → Read the docs
How It Works

Proximity Commerce

Three-step autonomous transaction triggered by physical proximity.

Detect → Order → Ready
Detect
Agent senses proximity
Patty's agent detects she's within range via the cafe's .well-known/agent-payment endpoint.
Order
Pre-order placed
Agent reads preferences, places the order, and pays via x402.
Ready
Cup waiting on arrival
Cafe confirms preparation complete. No queue, no friction.
Details

Transaction Detail

Transaction

Zero-Friction Payment

Triggergeofence / BLE
Discovery.well-known/agent-payment
Payment railx402
Amount4.50 USDC
Confirmation< 2 seconds
Human interventionnone
Discovery

.well-known Endpoint

The cafe publishes a .well-known/agent-payment.json file at its domain. This tells any agent: accepted assets, pay-to address, PQ key, ZAP endpoint, and menu availability.

.well-known x402 PQ-ready