Your next wholesale customer will not have a face. It will be another company’s procurement agent — software that discovers your catalogue, checks the price, places the order, and never once loads your product page. A VBWD analysis argues that most B2B suppliers are building for a human buyer who is quietly being replaced by a machine, and that serving the machine directly is not a next-decade project. It is a set of switches on today’s stack.

The constellation: mcp exposes your catalogue as agent-callable tools, shop holds products and stock, token_payment meters and bills consumption, non-custodial crypto settles the money, and signed webhooks fire restock and fulfilment. VBWD is a self-hosted, source-available full-stack SaaS SDK, and the whole transaction happens with no human in the loop, reconciling as cleanly as a click.

The customer is software

In agent-native wholesale there is no cart abandonment and no product photography, because the buyer is a procurement agent optimizing on availability, price, and lead time. As the original analysis puts it:

It will be another company’s procurement agent — software that discovers your catalogue, checks the price, places the order, and never once loads your product page.

The shop plugin sits behind that surface holding real products, variants, orders, and stock. When the agent places an order through MCP, it draws down live inventory and produces a real invoice line item — the same point of truth every other VBWD transaction uses, so there is no separate “agent order” ledger to reconcile.

Metering, because agents buy continuously

Human wholesale is lumpy; agent wholesale is continuous and volume-sensitive, and that is where token_payment earns its place with metered credit billing. A procurement agent tops up a balance and every order meters against it — you price by volume, tier, or usage without inventing a billing engine. It also gives you a natural trust boundary: an agent can only spend the credits its owner funded. Because credits and orders are both line items on the same invoice, a finance team on either side reads one document.

Settlement and signed events

Money between companies is where B2B slows to a crawl. VBWD’s payment core is provider-agnostic, and non-custodial crypto settlement lands funds directly in your own merchant wallet, programmatically, with no custodian holding float — settlement at machine speed. If a buyer needs cards or a regional rail, that is another provider on the same core.

An order still has to move atoms, and the event-driven core handles that. The original is blunt about why the signature matters:

The signature matters — because the buyer is software and the trigger is software, you need cryptographic proof that a fulfilment event genuinely came from your platform and was not spoofed.

Signed webhooks give downstream systems that assurance, so discovery, purchase, payment, and fulfilment become one unbroken, auditable flow.

Trust is the product, not a toggle

Here is the caveat, and in agent-native commerce it is the whole ballgame. VBWD gives you the discoverable catalogue, the metered billing, the settlement, and the signed events. It does not decide which agents you trust, how you authenticate the company behind an agent, or what limits you place on autonomous spend. When your customer is software, your trust-and-safety model — credential issuance, rate limits, anomaly detection, dispute handling for orders no human reviewed — is the differentiated product you must build. The platform makes each transaction verifiable; it does not underwrite the counterparty. You also still run sourcing, pricing, logistics, and the deployment.

What makes it credible today is that every component ships — the MCP server is agent-callable now, and the platform has already carried a pharmacy shop, dataset publishing, a dice-market game, and a tarot app. Read the full analysis on VBWD, or pull the public SDK.

Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.