A self-hosted, members-only marketplace for tokens, files and datasets — with LLM agents doing the admin through a safe, permissioned interface. Here’s how the pieces fit, and why the boring plumbing is the part you no longer have to build.
A private marketplace where members trade tokens, files and datasets — and AI agents safely do the admin — is now something you can self-host.
“You can’t run your own exchange — that’s what platforms are for.” That assumption is exactly why most people still rent someone else’s rails and hand over custody of their users’ money, files and data. A new technical walkthrough argues the opposite: a private, self-hosted marketplace where members trade tokens, files and whole datasets — and where LLM agents safely do the admin — is now something you can stand up on infrastructure you control.
Three asset types, one ledger
The idea is a members-only exchange with three kinds of tradable asset: an internal token/credit, encrypted files, and datasets sold as metered access rather than a raw download. The trick that keeps it coherent is refusing to treat them as three separate systems. As the original analysis on VBWD puts it:
a token, a file and a dataset are not three separate money systems bolted together; they are three kinds of line item on the same ledger, priced, taxed, discounted and settled the same way.
On the self-hosted, source-available VBWD platform, each capability is a switch-on plugin: token_payment for the credit economy, office for encrypted files, dataset for licensed data, marketplace to let any member list and buy, withdraw for payouts, and non-custodial crypto so settlement lands in the user’s own wallet instead of the operator’s — the difference, for an asset exchange, between running software and running a money-transmitter.
Where the AI agents come in
The part that makes this more than a marketplace is the operator layer. VBWD’s MCP plugin is an agent-callable capability server:
it turns platform actions into tools an LLM agent can discover and invoke through a clean, safe surface, instead of driving a browser.
An agent can check a balance, grant a dataset entitlement, move a file or execute a trade — and because it acts under role-based access control, it can do exactly what its role allows and nothing more. Every action lands as an invoice line item on the same ledger, logged by the event-driven core, so there is one audit trail to review rather than a separate “agent actions” database drifting away from the real one. Give members a natural-language front door and a user can simply tell their agent to sell a dataset and move the credits to their wallet.
Why private and self-hosted is the point
For an exchange of tokens, files and data, the walkthrough is blunt about why you host it yourself:
self-hosting is not a preference — it is the trust model.
Balances, encrypted files and datasets stay inside a perimeter the operator controls, the code is open to audit, and non-custodial settlement means nobody is holding other people’s money. The honest caveat is that a framework gives you the plumbing — the multi-asset ledger, encrypted storage, metered access, payouts and the agent interface — but not the business or the legal opinion. You still design trust-and-safety, decide what may be traded, and get real advice on how tokens and payouts are regulated where you operate.
The full step-by-step — which plugins to enable and how the agent layer stays safe — is published on VBWD; the platform’s public SDK is on GitHub.
Written for Red Robot with AI assistance and human editing. Adapted from an original analysis published on VBWD.
