Agent Hardware Store
One funded endpoint. Every tool your agent needs.
Give an agent a single MCP URL with a budget attached. It can search the catalogue, buy what it needs, and call it — without ever holding your credentials or your credit card.
For humans
You hold the wallet. The agent holds a URL.
Money and permission stay on your side of the line. The agent only ever gets an endpoint with a ceiling on it.
Add funds
Top up your account balance through Stripe. Your balance is the sum of an append-only ledger — every credit and debit is a row you can account for.
Create an agent endpoint
Each agent gets its own URL and its own allocation in cents. Spending is checked against that allocation on every call, so an agent cannot outrun its budget.
Paste the URL into your agent
Any MCP client that speaks streamable HTTP works. Pause an endpoint, change its budget, or delete it whenever you like.
For agents
Four tools behind one endpoint
Your agent connects once. Everything on the marketplace is reachable through the same four tools — no per-service setup, no second set of credentials.
search(query)Finds live listings, with price and whether the account already owns them.
get_mcp(listing_id)Returns the listing’s tool schemas from our cache, so discovery costs nothing and never depends on an upstream being awake.
purchase(listing_id, expected_price_cents)An explicit purchase, never automatic. The agent has to echo back the price it saw; if the price moved, the purchase is rejected instead of guessed at.
execute(listing_id, tool_name, args)Runs a tool on the purchased MCP. Out of budget or missing an authorization, the agent gets a plain answer telling it what to ask you for.
Control
What stops an agent from spending your money badly
A prompt-injected agent is a real risk, so the limits are structural rather than advisory.
A hard ceiling per agent
Every call reserves against that endpoint's allocation in a single atomic check. Concurrent calls cannot race past the limit.
Purchases are explicit and price-checked
There is no auto-buy. An agent must call purchase with the price it was quoted, and a changed price stops the transaction.
Authorizations you can see and revoke
MCPs that act on your accounts use tokens held server-side on your behalf. The connections page lists every one, with a revoke button.
Upstream details stay upstream
Agents never receive an upstream URL, identity, or raw error. Developer keys and your OAuth tokens are encrypted and only ever used server-side.
For developers
List a hosted MCP and get paid for it
Bring a reachable MCP server. We handle discovery, billing, and the buyer relationship; you take a revenue share on every purchase.
Two integration types
Supply one platform API key and buyers can use your MCP the moment they buy, or use OAuth passthrough so each buyer authorizes their own account.
Submit, validate, review
We check your server is reachable and pull its tool schemas automatically, then a human reviews the listing before it goes live.
Payouts via Stripe Connect
Onboard once through Stripe and get paid out directly. No invoicing us for your own revenue.