Engineering-as-marketing works when the tutorial is the product’s first mile. This is that mile. You will not launch an “agent protocol company.” You will make one route refuse to run for free.
Scope (what to skip)
- Skip accounts for the agent beyond the Vybe pay handshake
- Skip a dashboard redesign
- Skip metering twenty routes
- Skip wrapping a markdown file and calling it commerce
The build
- Choose a route with a clear JSON output.
- Set a price you’d actually collect.
- Add vybe402 (or requireVybePayment) so unpaid traffic gets 402.
- Call it without payment. Save the response.
- Settle. Retry with proof. Confirm 200 and a single handler run.
- Confirm your Collect/Wallet balance moved—or the seller you pointed at did.
One boring paid call beats a deck about agentic commerce.
Snippet library (mental copy-paste)
Middleware in, route unchanged, price in config. That’s the library we want people to bookmark. Full SDK surface is on the developer page and waitlist. The weekend test is local.
When that’s green, list the SKU next to your human offerings. Same @you. Same catalog. Then join the list if you want session keys and ACP paths as they open.
