Curated machine-payable vendors.
Every paid upstream an action can reach, vetted and listed here. If a vendor is not on this page, the platform treasury will not pay it — and an action cannot spend a cent on it.
Curated twice
An action is vetted by Wandlet, and every paid vendor it touches is curated by Wandlet. Both checks run before anything is listable.
Priced before you run
Every run shows its estimate first — credits in the Wandlet menu, dollars on an agent's MCP quote. Spend never exceeds the ceiling you authorized; the rest refunds.
Receipted after
Every run returns an itemized receipt naming the vendor, the real upstream price, and every other line — the lines sum to the total, by construction.
Any rail in, one rail out.
-
01
You pay your way
Top up a Wandlet balance with a card, or pay per cast over x402. Your choice never limits which vendors an action can use.
-
02
The platform pays the vendor
When an action calls a paid API, Wandlet's treasury answers the vendor's 402 quote automatically, inside a per-destination spending cap. The action never handles payments; you never see a wallet prompt.
-
03
The receipt proves it
The vendor's real charge lands on your receipt as its own line, with the payment reference. The unspent part of the estimate refunds automatically.
The quiet consequence: this makes any x402-capable API payable with a credit card, through an action. Agents get the same catalog over MCP →
Curated vendors, by category.
Statuses are honest: vetted means the treasury pays this vendor today. in evaluation means it is being tested — actions cannot spend on it yet. suspended means payments are stopped, fleet-wide, effective on the next run.
The bar a vendor clears.
- Legitimacy. A real operator, a real service, terms we have read.
- Transparent pricing. Machine-readable quotes; the price quoted is the price paid.
- Stability. Tested under our own actions before any customer's run touches it.
- Clean failure. Errors are typed and refundable — a failed call must not eat a payment silently.
- Suspendable in data. A vendor incident flips one status flag and takes effect on the next run, fleet-wide — a data update, not a deploy.
- Named on receipts. Every charge traces to the vendor's registry entry, even on a detached receipt.
Run an API? Get listed.
x402-enable your endpoint and apply. Listed vendors get paid per call by the platform treasury, discovered by every agent on the MCP surface, and named on every receipt.
Reach us through the contact in the legal notice.