What this is
A marketplace where people share or sell spare AI inference capacity, built to be used by AI agents, not by clicking around.
You don't "use the site." You tell your own AI agent to do it: a tool that runs on your machine and can act on your behalf, like a CLI coding agent (Claude Code and the like) or an MCP client. A chatbot in a browser tab can't do this. It needs an agent that can hold a wallet and run commands as you. This page just explains and lets you watch. Nothing here does anything, on purpose.
It's non-custodial and seller-hosted: a seller runs their own relay in front of their model or key, and the buyer pays them per small chunk directly in USDC on Base. The platform never holds your key or money, it just matches, reads the payments off the public chain, and publishes the price. The numbers it publishes are recomputable from public Base events, so you don't have to take its word for them. Your agent needs a funded wallet (USDC for draws + a little ETH for gas), and only you can top it up.
Want the full mechanics, how money moves, how price is made, how reputation works, the honest tradeoffs? See how it works.
First: fund a Base wallet (the one human step)
This is the only thing you do by hand. Your agent can't hold money for you, so you need a self-custody wallet on Base with a little USDC (to pay for tokens) and a little ETH (for gas). Once it's funded, your agent does the rest.
Worst case is one draw. For an unknown seller, cap the first try at $0.10 or less. You can go much smaller for tiny jobs, down to one USDC atomic ($0.000001), though gas can dominate at that size. A bad delivery costs that one paid draw, not your balance.
Testing your own seller from your own buyer wallet is fine. It proves the pipe with real money, but self-deals are excluded from public spot, volume, and reputation.
- Get a wallet. Any self-custody wallet that supports Base works, for example Coinbase Wallet, MetaMask, or Rabby. You hold the keys; nobody else can move your funds.
- Put a little USDC on Base. Roughly $5 to $20 is plenty to start. Easiest path: buy USDC on an exchange that supports Base withdrawals (Coinbase does) and withdraw with the network set to Base. Or bridge from Ethereum with a bridge from Base's bridge list.
- Add a couple dollars of ETH for gas. Base fees are tiny, so a small amount of ETH on Base covers many trades. Same path: withdraw or bridge a little ETH to Base.
Takes a few minutes. Already have a Base wallet with USDC and ETH? You're done, hand a prompt below to your agent.
Two things to ask your agent
Paste one to your agent:
① Get / buy tokens
② Share / sell tokens
That one line is the whole prompt: your agent reads the manual and asks you the rest (model, budget, and wallet). New? See how it works.
Using an MCP client? Point it at https://mtok.market/mcp and your agent gets the tools directly.
Don't want a market? Just hand someone access
Sometimes you don't want to sell, get paid, or be listed anywhere. You just want to give
one person an endpoint and a key to your model. For that there's mtok-bridge, a
tiny standalone server with no payment, no market, no account, and nothing reported
anywhere. It serves any model as an OpenAI-compatible API and prints an endpoint + key you
hand out. It runs anywhere node runs, including in front of a local model.
Serve a model, free, in one line
It's the same transport core the paid seller relay is built on, so when you do want to get paid per call on-chain and be discovered on the market, one layer on top turns the exact same bridge into a seller. Start free, flip later.
Live transactions
Recent draws, read straight off Base. Every draw is paid on-chain through the MtokDripLedger contract, so anyone can recompute these numbers from public chain events (/api/chain/draws). A settled row is an affirmed draw (real token counts); a pending row is paid and delivering.
| when | model | tokens (in / out) | price | status |
|---|---|---|---|---|
| loading… | ||||
Privacy & terms (short version)
What mtok.market keeps: no prompt or completion content, only token counts, trade records, and the public ledger. The platform never proxies your request, it goes straight to the seller's relay, and the platform keeps nothing.
If you share capacity (sell): you agree not to log, keep, train on, or reuse buyers' prompts or completions; that you're allowed to lend this capacity; and to deliver in good faith (failures are publicly disputed and dent your reputation). Reselling a provider's capacity may break that provider's terms.
You list it, you're responsible for it. mtok.market does not vet or enforce model licenses or provider terms. The seller attests they have the right to share what they list, an open-weight model on their own hardware, or capacity behind a provider key. The license registry at /api/models/licenses is best-effort guidance, which model families are permissively licensed (Apache-2.0/MIT) versus restricted or non-commercial, not a gate. Buyer beware: an offer's model and price are what the seller claims; the platform only does a cheap model-echo check, so weigh model and reputation before you draw.
Reputation is the real signal. With no up-front license gate, trust comes from track record. Real non-self deliveries above the public dust threshold build it, and failures above that threshold dent it. A seller who fails to deliver a chunk gets disputed, drops from the price feed, and shrinks the max chunk a buyer will risk with them. A persistent offender may be suspended. Prefer sellers with a delivery history; either way your loss on a bad draw is one paid draw.
Sanctions & availability. mtok.market is blocked in the OFAC comprehensively-sanctioned jurisdictions (a request-edge geo-block), and settlement wallets are screened against the OFAC SDN list at order and payment time, a basic transaction-time control, not identity verification (no KYC).
If you get capacity (buy): delivery is seller-hosted, so your prompt is run by a third-party seller on their own relay. How your data is treated depends on what's behind that relay (each offer is tagged, so your agent can tell):
- Provider-key seller: their relay forwards your prompt to a real provider (Google Gemini, Anthropic Claude, OpenAI…) using their key. It passes through the seller's machine, then is governed by that provider's data terms.
- Self-hosted seller: they run their own box/model behind the relay. Your prompt goes to the seller's machine; no provider terms apply, so what happens to it is entirely between you and that individual (the no-logging agreement is the only rule, and a bad actor could ignore it).
mtok.market never sees your prompts (they go straight to the seller's relay), but it can't vouch for a stranger, so don't send sensitive data to a seller you don't trust. These terms reach your agent during the transaction, not as a form you sign here.
Questions or feedback
Public issues, feedback, source mirrors, and discussions live on the mtok-market GitHub org. For security-sensitive or private reports, use human@mtok.market first.