Built so a well-behaved AI agent can buy training the same way a person can.
The VR Hub subscribe page exposes structured pricing and settles in USDC on Base. That means an AI procurement assistant working on behalf of a training coordinator can quote, purchase, and confirm a subscription without a human filling in a form.
Why this exists
Over the next few years, procurement is going to change shape. Companies are already handing agents the task of shopping for compliance training, safety courses, and skills programs on behalf of their teams. Those agents need three things a normal e-commerce site does not provide:
- Machine-readable pricing. Not screenshots of a pricing page, not "contact us for a quote" — actual structured data an agent can parse.
- Programmable payment. A settlement rail that works in seconds, at any hour, without a human clicking through a credit-card form.
- Verifiable receipt. A record the agent can hand back to whoever sent it, showing what was purchased and confirmed on-chain.
We built the VR Hub checkout to give agents all three. Human checkout still works the way it always has.
What's on the page
1. Structured product data (Schema.org)
The subscribe page emits a Schema.org Product block with every pricing tier, quantity range, and accepted payment method. Any AI system that reads Schema.org — most of them — can build an accurate quote without human parsing.
To inspect it: view source on /hub/subscribe.html and look for <script type="application/ld+json"> in the head.
2. USDC settlement on Base
Human buyers can pay with PayPal or USDC. Agents will use USDC. Base is Coinbase's Ethereum L2, chosen because it settles in seconds, costs cents in gas, and is compatible with every major wallet an agent might carry.
3. A quote endpoint an agent can call
The checkout backend accepts a POST with the buyer's context and returns a locked USDC quote plus a receive address and order ID. The agent then executes the transfer from its wallet, POSTs the transaction hash to the capture endpoint, and gets a confirmation record. Fields required to reserve the order are documented in the subscribe page form: a contact name, email, address, chosen location count, and terms acceptance.
/pay endpoint scoped for machine callers (no form fields, just SKU + quantity) is on the roadmap. Until it lands, agents can drive the same backend the human UI uses. If you're building an agent that wants to purchase VR Hub training, get in touch and we'll walk you through it.
How this maps to what's happening in the industry
Marc Andreessen has been arguing that AI is crypto's killer application: the reason crypto matters isn't that humans want to pay in it, but that agents genuinely need programmable, native-internet money to transact on our behalf. Jordi Visser makes a similar point — that agents, not humans, will be the biggest users of stablecoins over the next decade. HTTP even reserved status code 402 ("Payment Required") back in 1997, and it sat unused for 28 years because there was no way for a machine to actually pay. There is now.
We are not saying every training buyer needs to pay in USDC today. Most will pay by credit card or PayPal for a long time. But when the buyer is a machine — and that shift is starting to happen — we want VR Hub to be one of the vendors it can actually check out on.
What we do not do (yet)
- x402 headers. We haven't implemented the x402 HTTP-402 flow on gated resources. It's on the near-term list for pay-per-request assets like course previews.
- Tokenized completion certificates. Pioneer Pass NFTs are on-chain today; per-course completion credentials on Base are on the 2027 roadmap.
- Programmatic seat provisioning. After payment, seat setup and welcome email still touch a human at Melcher Studios. Fully automated provisioning is planned.