Say what you want. Borneo routes wallet liquidity into USDT0, settles via x402, and credits network ownership — open to any HTTP agent, not locked inside two chat apps.
The problem
Buying merch or tokenized assets usually means multi-step conversions and separate rails — while open HTTP agents still cannot reach inventory locked inside two chat apps.
Intent → Route → Settle → Own
One agent loop on X Layer
Borneo evaluates the wallet, routes liquidity into USDT0, settles with OKX x402, and accrues network ownership from the protocol fee — so switching is seamless and rewarded.
N
Tokens in the wallet
ETH, OKB, alts — fragmented for commerce
1
Settlement asset on X Layer
USDT0 via x402
+
Ownership on every buy
Protocol micro-fee → network stake
What exists today
Stripe-style agent commerce lists products where ChatGPT and Claude can reach them. Everything else is locked out.
Closed path
Blocked
Why it loses
Borneo
Publish once. Humans shop in chat. Procurement bots, local LLMs, and personal agents hit the same /api/search and settle USDT0 via x402.
Publish
registry · llms.txt
Discover
GET /api/search
Any HTTP agent
procurement · local · personal
Settle
USDT0 · x402 · POST /buy
Any agent can call
No ChatGPT or Claude gate
Publish registry and store llms.txt. Not trapped inside ChatGPT or Claude — open to procurement, local, and personal agents too.
Tell the agent what you want on. It ranks live SKUs via /api/search — the same endpoint external agents use — then settles in chat.
No-code for a single shop. The same chat for a retailer with many locations. Upload a catalog, connect an API, or just type.
Type inventory, drop a CSV, or paste a store URL. No admin form marathon.
50 shirts · size M · wallet boundChat, file upload, or API pointer. Same path for a single shop or a multi-location retailer.
CSV, Shopify URL, or chatPublished store sits on the open registry. Any HTTP agent can search and buy — not only ChatGPT or Claude.
GET /registry.json · GET /api/searchOccasion-aware shopper — then ranks via protocol search, not HTML scrape or a walled agent store. Checkout stays in chat: authorize once, settle USDT0 via x402.
I want to shop
You
Buy this limited drop — pay from my wallet.
Agent
Matched the drop. Checking USDT0 — will route OKB → USDT0 on X Layer if short.
You
Authorize.
Agent
Routed liquidity, settled x402, credited network ownership.
HTTP 402 / x402 on X Layer — no redirect checkout tab. The agent only settles after you authorize. Locked quote: payee, amount, and SKU cannot be rewritten by catalog copy.
x402, agent-ready
Challenge → authorize → settle USDT0 to the merchant wallet. Same path for the fashion chat and any external HTTP agent.
402 → PAYMENT-SIGNATURE → 200
USDT0 on X Layer
Stablecoin settle on testnet — exact amount, locked payTo, explorer receipt after success.
POST /s/{slug}/buy
Every purchase opens a preview. You see the item, the merchant, the amount, and the rail. Catalog copy cannot change those fields or skip authorize.
Identity first
Merchants prove a wallet before a store publishes. Buyers stay in a named session.
Transaction preview
Item, merchant, amount, and rail are visible before anything moves.
Confirm, then pay
The agent does not transact until you tap Authorize purchase.
Catalog cannot retarget
Store titles and llms.txt are data only. They cannot change payee, amount, or skip authorize.
What you confirm
Quote locked at authorize. PayTo and amount cannot change from catalog text. Confirm once — then settle on the ledger.
I want to shopSearch. Intent ranking over the live market via GET /api/search — humans in the buyer chat and external agents share one path.
Open protocol. Registry and store llms.txt are HTTP, not app-gated. Procurement, local, and personal agents are first-class.
Settle. USDT0 via HTTP 402 / x402 on X Layer. Waits on explicit authorize — catalog copy cannot retarget pay.
Borneo
Publish once for every agent. Sell first — shoppers follow. Two doors, separate accounts.
