Overview

What datapoint.market is

A hosted paid relay for APIs and MCP tools. You point it at an origin (your real API, or an upstream MCP server), set a price, and datapoint.market gives you a URL that charges callers per request in USDC and forwards to your origin only after payment settles on-chain.

Payment uses x402 — the HTTP 402 Payment Required standard for machine payments. The caller doesn’t need an account, an API key, or a credit card: they sign a stablecoin authorization and attach it as a header.

Why it’s agent-native

Buyers need no account. An agent hits a URL, gets a 402 with a machine-readable price, pays, and retries. The whole loop is HTTP + a signature.
Providers can be agents too. A provider can onboard with just a wallet signature, or connect datapoint.market in Claude over MCP and create/manage endpoints from a chat.
Non-custodial. datapoint.market never holds funds. An immutable on-chain splitter contract pays the provider and the protocol fee in the same transaction, straight from the buyer.

The two roles

Role	Who	What they do	Auth
Buyer	any human or agent	call a paid endpoint, pay per request	none (raw x402), or an account whose connector buys from a managed wallet
Provider	publishes endpoints	create/manage relays, MCP wrappers, datasets; get paid	session, OAuth (connect in Claude), or wallet → automation key

The roles aren’t separate apps: the same connector an account uses to sell can also discover and buy — see Buying with the connector.

The products a provider can publish

API relay (/r/{provider}/{endpoint}) — wraps one HTTP origin (GET/POST), one price per call.
MCP wrapper (/m/{provider}/{server}) — wraps an upstream MCP server and prices each tool individually; an x402-aware MCP client pays per tool call.
Dataset — an API relay whose origin returns a download link; the buyer pays once for a file. See Selling datasets.

Don’t confuse these with the management MCP (/mcp) — that’s the control plane an agent uses to create, manage, and buy, not a paid relay.

Mental model (one diagram in words)

Buyer agent ──GET──▶ /r/acme/weather
            ◀─402──  { price: 0.05 USDC, network, asset, payTo: <splitter> }
Buyer signs an authorization (EIP-3009 on Base / Soroban auth on Stellar /
            a partial-signed SPL transfer tx on Solana)
            ──GET + X-PAYMENT──▶ /r/acme/weather
                                  relay: verify → settle on-chain (splitter pays
                                  provider + fee atomically) → forward to origin
            ◀─200 + result + X-PAYMENT-RECEIPT──

Status

Live on Base mainnet, Stellar pubnet, and Solana mainnet. Settlement, both on-ramps (API relay + MCP wrapper), the marketplace, and the management MCP (with “connect in Claude” OAuth) are all shipped. See Networks & assets for exactly which chains are wired.

Next: read Concepts for the moving parts, or jump to a guide.