PitWire: the market wire AI agents pay to read

The problem

Your next customer is a script. It can't sign up.

AI agents are becoming real buyers of data, but every feed worth having sits behind plumbing built for humans.

API keys assume a humanSign-up forms, KYC, dashboards, monthly invoices: an autonomous agent can operate none of it. Data behind a login might as well not exist for the agent economy.

Subscriptions don't fit machinesAn agent needs one answer, once, at 3 a.m., not a seat, a tier, or an annual contract. Per-request pricing is the only shape that matches how agents consume.

The data itself is scatteredPrice on a DEX, volume in contract events, holder flows nowhere. An agent burns half its budget stitching five sources into one answer.

PitWire collapses all three. Unified on-chain Stock Token data, sold per request over plain HTTP: the wallet is the account, the 402 is the contract, 0.001 USDG is the invoice.

How agents pay

Four steps. No accounts. Machine speed.

x402 turns HTTP's forgotten status code into a payment rail. The whole exchange is two requests, and the payment is gasless for the agent.

Request

The agent calls a priced endpoint like any HTTP API.

GET /v1/price/NVDA

Challenge

The server answers 402 with exact payment terms.

402 · 0.001 USDG
→ payTo, asset, network

Sign

The agent signs an EIP-3009 transfer: an offline signature, no gas.

signTypedData(
  TransferWithAuthorization)

Data + receipt

A facilitator settles on-chain; data returns with the tx hash.

200 OK
PAYMENT-RESPONSE: tx 0x…

Claude integration

Ask Claude. Claude pays. You watch the receipts.

An MCP server with a paying wallet built in. Add it to Claude Desktop or Claude Code, then just ask: "What's NVDA trading at, and how good is the data?"

{
  "mcpServers": {
    "pitwire": {
      "command": "npx",
      "args": ["-y", "@pitwire/mcp"],
      "env": {
        "API_URL": "https://pitwire.xyz",
        "PRIVATE_KEY": "0x…a small, dedicated wallet",
        "MAX_SPEND_PER_HOUR": "0.25"
      }
    }
  }
}

Hard spend limitA sliding one-hour cap enforced in the payment core: no tool can exceed it, no loop can drain the wallet.

Every payment visibleEach response carries spend-this-call, session total, and wallet balance. Nothing happens off the books.

Sandboxed walletFund it with 5–10 USDG. Never connect a main wallet; the docs say it, the defaults assume it.

Docs

Everything an agent builder needs.

Three commands to run it locally, one table to price it, one table to trust it.

Quickstart

# 1. See what's for sale (free)
curl https://pitwire.xyz/v1/tokens

# 2. Hit a priced endpoint: the 402 response IS the integration guide
curl -i https://pitwire.xyz/v1/price/NVDA

# 3. Or skip HTTP entirely: add the MCP server to Claude (config above)

Endpoints

Endpoint	Price	Returns
`GET /v1/tokens`	free	Supported tokens + price list (discovery)
`GET /v1/price/:symbol`	0.001 USDG	TWAP price, 24h change, quality score, pool, tx receipt
`GET /v1/stats`	free	Live payment feed, revenue, leaderboard
`GET /v1/yield/opportunities`	soon	RWA vault comparison: the flagship, in progress

MCP tools

Tool	Payment	Does
`get_stock_price`	0.001 USDG	Price + change + quality for one symbol
`get_multiple_prices`	per symbol	Up to 10 symbols; stops cleanly at the spend limit
`list_supported_tokens`	free	Discovery: what's sold, at what price

Quality factors

Factor	Deduction	Meaning
`spot_price_no_twap`	−25	TWAP window unavailable; spot price used and labelled
`single_observation`	−30	Pool has cardinality 1; TWAP is idle extrapolation
`no_in_range_liquidity`	−25	No active LP at current tick; price is thin
`cross_rate_hop`	−5	Priced via WETH bridge; two pools multiply
`stale_data`	cap 40	Served from cache after an RPC failure, flagged

Protocol

x402 v2 over HTTP: PAYMENT-REQUIRED challenge, PAYMENT-SIGNATURE payload, PAYMENT-RESPONSE receipt. Settlement in USDG (EIP-3009) on Robinhood Chain (eip155:4663), gasless for the payer. Replayed nonces return the cached response without settling twice, so you can never pay twice for the same request.

Roadmap

From one priced endpoint to a data marketplace.

Built in deliberate phases; each one has to earn its exit criteria before the next begins.

PHASE 0shipped

De-risk

Facilitator verified live (x402 v2, Robinhood Chain testnet), end-to-end Hello-402 loop with real EIP-3009 signatures, monorepo + mock facilitator with nonce idempotency.

PHASE 1live

MVP: one paid endpoint

/v1/price/:symbol at 0.001 USDG, settle-then-serve, live payment feed and leaderboard, 30-line reference client. Deployed and taking payments.

PHASE 2in progress

Value layer

The flagship: /v1/yield/opportunities: RWA vault APY / TVL / risk comparison no free source returns in one request. Ponder indexer for holder flows, embedded signal scores. MCP tools shipped early with hard spend limits.

PHASE 3next

Distribution

x402 Bazaar + .well-known/x402 discovery listings, full public dashboard, and Base support, no longer optional: the wallet-holding agent wave settles where the ecosystem's mass is.

PHASE 4planned

Marketplace

Third-party publishers sell through PitWire; the platform curates, scores quality, and takes a 10–20% commission. The moat is the data product and its reputation layer, not paywall plumbing.

PHASE 5planned

Scale

Prepaid credit for high-frequency agents, subscriptions, paid websocket streams, enterprise SLA tier.

Why the urgency on Phases 2–3: with Cloudflare Wallets (Aug 2026) putting spend-capped x402 wallets in every developer's hands, the population of agents that can pay is about to grow fast. PitWire's job is to be listed where they look, with data worth paying for on the shelf.

The market wire
AI agents pay to read