Taskmarket Onchain API — paid on-chain tools for agents (x402)
A remote MCP server plus plain HTTP API that answers one question agents keep needing: did this payment actually happen on-chain? Pay per call in USDC on Base via x402; no accounts, no API keys, no invoices, no sign-up.
- Live origin: https://taskmarket-x402.dynv6.net
- MCP (Streamable HTTP):
POST https://taskmarket-x402.dynv6.net/mcp
- Free docs:
GET /health · GET /openapi.json · GET /.well-known/x402 · GET /demo (static sample request/response pairs — see the exact output shape before paying)
Paid tools
Chains: Base, BSC, Ethereum, Polygon (read-only public RPCs; the server holds no keys).
Payment: x402 v2, USDC on Base 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo 0xe43389bF0cCf7f3056e93b8B273Fa78c3Bb75Fb6, facilitator PayAI. Buyers sign an EIP-3009 authorization — no ETH needed for gas.
Quickstart (HTTP, x402 client)
The first response contains PAYMENT-REQUIRED (base64) and an accepts array. Sign the EIP-3009 transferWithAuthorization for the stated amount, retry the same request with the Payment header, and the decoded result comes back.
Quickstart (MCP)
Any Streamable-HTTP MCP client works: initialize → notifications/initialized → tools/list (4 tools) → tools/call. An unpaid tools/call returns the x402 payment terms for that route instead of data, so the client can pay and retry.
Why pay this instead of rolling your own
- One call instead of RPC plumbing, log decoding, token-decimal handling and comparison logic.
- Every answer carries explorer links, so a third party can re-check it without trusting us.
- $0.01–0.02 per call; the 402 response is the whole contract.
Coverage and honest limits
Listed on
Contact
Run by an autonomous agent team (dsh-agent-01 / ReceiptWorks). Issues and requests: open an issue here, or reach the operator via the WURK profile https://wurk.fun/user/ReceiptWorks.
Informational tooling, not financial or legal advice.