Where AI, Crypto, andWholesale Commerce Converge
AI agents pay for data access with crypto. No API keys. No OAuth. No accounts. Just HTTP 402 and an EVM wallet. The internet's native payment protocol meets wholesale food commerce.
Three Worlds Colliding
Each of these is transformative on its own. Together, they create something that didn't exist before: autonomous commercial agents with native payment rails.
AI Agents
Autonomous software that discovers products, evaluates options, and executes purchases without human intervention.
Crypto Rails
Base L2 provides sub-cent transaction fees and instant settlement. No credit card forms, no OAuth flows, no friction.
Wholesale Commerce
1,000+ premium specialty food products at bulk pricing. The supply chain that feeds restaurants, caterers, and retailers.
Autonomous Wholesale Purchasing
An AI agent discovers truffle oil at wholesale prices, pays $0.001 for catalog access, builds a $2,000 wholesale order, and routes the buyer to checkout. No human touched a keyboard.
How It Works
Five steps from discovery to checkout. No API keys, no accounts, no friction.
Agent discovers BoxNCase
Via MCP server card, API catalog, or agent skills index. The agent finds our catalog endpoints.
/.well-known/mcp/server-card.jsonAgent requests catalog data
Calls /api/x402 to access wholesale product catalog. Server responds with HTTP 402 and payment requirements.
HTTP 402 + X-Payment headerAgent pays on Base
$0.001 per request, settled instantly on Base L2. No approval flow, no API key, no account creation.
EVM transaction on eip155:8453Agent receives data
Full catalog access unlocked. Agent searches products, compares prices, builds wholesale orders.
JSON response with catalog dataAgent creates checkout
Via UCP/ACP protocols, the agent creates a checkout session and redirects the buyer to complete the purchase.
checkout.boxncase.comProtocol Flow
AI Agent BoxNCase /api/x402 Base L2
│ │ │
│ GET /api/x402 │ │
│ ────────────────────────────► │ │
│ │ │
│ ◄── HTTP 402 Payment Required │ │
│ X-Payment: { │ │
│ scheme: "exact", │ │
│ price: "$0.001", │ │
│ network: "eip155:8453", │ │
│ payTo: "0xFC0b...8D24" │ │
│ } │ │
│ │ │
│ Transfer $0.001 USDC ─────────────────────────────────► │
│ ◄──────────────────── tx receipt ────────────────────── │
│ │ │
│ GET /api/x402 │ │
│ + X-Payment: {tx_hash} │ │
│ ────────────────────────────► │ │
│ │ verify payment ────► │
│ │ ◄── confirmed │
│ ◄── HTTP 200 + catalog data │ │Why This Matters
No API Keys Required
Traditional APIs require registration, key management, rate limit tiers, and billing agreements. x402 replaces all of that with a single payment per request.
Micropayments That Work
At $0.001 per request on Base L2, the transaction fee is negligible. Credit cards can't do this. Traditional payment rails have minimums. Crypto doesn't.
Permissionless Access
Any agent, anywhere in the world, can pay for access. No geographic restrictions, no approval queues, no vendor relationships needed.
Machine-Native
HTTP 402 was designed for this in 1997 but never had the payment infrastructure. Crypto on L2s finally makes it practical. The web is completing its original vision.
Build With x402
The endpoint is live. Point your agent at it. If it supports x402, it just works.