bots.st/mtok-market
mtok.market
Buy and sell AI inference token draws in USDC
1880 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 13
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mtok.market/mcp
What it can do
| Tool | What it says it does |
|---|---|
buying_guide | Turnkey, executable steps to get a human cheap AI tokens and run their prompts on mtok.market: bid (read routes[]) or read the book for a tier:direct offer, then draw paid chunks from the seller's relay (pay each draw on-chain through MtokDripLedger, POST <relayEndpoint>/chunk, the relay verifies… |
cancel_order | Cancel one of your open orders. side: offer|bid. |
get_book | Open offers (asks) and bids for a model. sort=input|output ranks by that dimension. |
get_config | Chain config a SELLER-HOSTED buyer needs to build the on-chain draw payment: { feeAddress, feeBps, dustThresholdUsd, chainId, usdcAddress, dripContractAddress }. Pay each draw through the MtokDripLedger contract at dripContractAddress (payDraw), then affirmDraw/disputeDraw on-chain; the seller… |
get_draws | The chain-derived draw tape: contract-paid draws indexed from MtokDripLedger events on Base. status=inProcess (DrawPaid with no terminal yet) | settled (closed by DrawAffirmed or DrawDisputed). This is the canonical delivered/receipt surface; the platform records nothing off-chain. |
get_me | Your agent state: open orders (offers + bids). Non-custodial — there is no platform wallet, grant, or credential vault in /me; money moves peer-to-peer on-chain, and your delivered draws are the on-chain tape (get_draws). |
get_reputation | A seller's reputation: score, tier, recommendedMaxChunkUsd (the per-draw size a buyer should risk in the direct tier), plus a chain object {affirmed, disputed, deliveredUsd} folded from MtokDripLedger events (source:"chain"). |
get_spot | Spot prices per model: the delivered OUTPUT-token rate (USD/MTok) from affirmed on-chain draws (last price, median, draw count). |
get_stats | Exchange fee model plus chain-derived volume: delivered volume + affirmed/disputed counts, all recomputable from MtokDripLedger events on Base (source:"chain"). |
place_bid | Bid for a block. The bid response returns routes[] — the crossing SELLER-HOSTED offers (lowest price first), each {offerId, sellerId, relayEndpoint, settlementPubkey, requestHashScheme?, inputPricePerMTok, outputPricePerMTok, availableInputTokens, availableOutputTokens}. Pick a route and DRAW paid… |
place_offer | List capacity for sale via SELLER-HOSTED delivery (tier:"direct" — the only advertised path). Set tier:"direct" + relayEndpoint (your relay's PUBLIC HTTPS url — a cloudflared tunnel gives one free) + settlementPubkey (your seller payout EVM address on Base) and NO credentialId: you run your own… |
register | Create an agent identity. Returns {agentId, apiKey}; send the apiKey as the x-api-key (or Authorization: Bearer) header on EVERY subsequent request to act as that agent — this transport is stateless, so it is not remembered between calls. Pass pubkey (Ed25519 SPKI PEM) if you will place signed… |
selling_guide | Turnkey, executable steps to put a human's spare AI capacity on mtok.market via SELLER-HOSTED delivery — run YOUR OWN relay pointed at an upstream you control (a local Ollama/vLLM model, a subscription via a CLI bridge, or a provider key) and list a tier:direct offer; buyers pay you per chunk… |
In its maker's words
Spot market for AI inference tokens. Buyers pay per draw in USDC on Base; sellers host delivery.
- Website
- mtok.market
- Source
- github.com/mtok-market/mcp
- Publisher
- mtok.market
- Listed from
- the official MCP Registry as
market.mtok/mcp - Version
- 1.0.1, updated 8 Jul 2026
- Kinds of work
- Shops and payments, AI models and agent tools, Browser and automation
The domain it lives on
- mtok.market
- registered 13 Jun 2026 (5 months ago), at Cloudflare, Inc, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1880 ms | |
| Answered | 2352 ms | |
| Answered | 903 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.