Cashboard Signals: market data your agent pays for per call

There are five paid tools and two free ones. Every paid tool reads public data, adds Cashboard's own computation where the tool says so, and returns the same kind of answer: the data, the time it was observed, the sources it came from, and whether you were charged. No tool trades, signs or reads anything from a Cashboard board.

Arguments

What a result looks like

Token names, symbols and market names in a result are data from the chain or a venue, and can hold any text. The tool descriptions tell the agent to treat them as data, not instructions. Whether the agent obeys is up to the agent.

Add the MCP server to Claude Code with one command. It needs no wallet and no key, and it gives the agent cashboard_catalog and cashboard_sample next to the five paid tools.

claude mcp add --transport http cashboard-signals https://cashboard.live/mcp

• Each address gets 25 free samples per UTC day, and all addresses together get 1,000 a day. The counter resets at 00:00 UTC, and the catalog shows how many you have left.
• A sample is served from the same cache as a paid call, with the same freshness, so it is a fair preview of what you would pay for.
• Samples use the same per-minute limits as paid calls, and a sample of an incomplete result is returned with its note like any other result.
• The paid tools themselves always ask for payment when called without one. A sample is only reachable through cashboard_sample.

Other MCP clients connect the same way: point them at https://cashboard.live/mcp as a remote server over HTTP. Nothing is stored between calls, so the server keeps no session.

Payment uses x402, which turns an HTTP 402 Payment Required answer into a USDC payment your agent signs and sends with its next request. You need a wallet with USDC on Base or on Solana. You sign a transfer authorization and the payment facilitator submits it, so the wallet needs USDC but no ETH or SOL for fees.

1. 1

   Give the agent an x402 wallet

   Use an MCP server or client that can pay x402 requests, such as Coinbase payments-mcp or agentcash. Fund its wallet with USDC on Base or Solana.

2. 2

   Call the HTTP route of a tool

   The wallet requests https://cashboard.live/x402/<tool> with the arguments in the query string, receives the price, signs a payment and repeats the request with a PAYMENT-SIGNATURE header. The routes are perp-scan, oi-movers, funding-extremes, wallet-swaps and chain-pulse.

3. 3

   Read the result and the receipt

   A complete result comes back with a PAYMENT-RESPONSE header that holds the receipt. See Receipts below.

The MCP tools answer a call that has no payment with an error result that carries the same payment requirements, a line that says the price, and the HTTP route to pay at. A client that supports the x402 MCP transport can attach its payment to the tool call in _meta["x402/payment"] instead, and gets its receipt back in _meta["x402/payment-response"].

The HTTP routes

The routes accept GET only. They set no cross-origin headers, so a web page cannot call them from a browser, and an MCP request carrying another web origin is refused. Arguments go in the query string. A list is comma-separated, and the conditions of perp-scan is a JSON string, URL-encoded. wallet-swaps needs chain=solana.

https://cashboard.live/x402/funding-extremes?side=both&minOiUsd=5000000&limit=10
https://cashboard.live/x402/chain-pulse?chain=base
https://cashboard.live/x402/wallet-swaps?chain=solana&wallets=FKQ443z3YMbfgCu2EUmBezALsKEV8225qv9k7xej4vS1,FSYKJo8zwVX2CHwjKk2rChi9Vsg2nNvaR6SRH1u2edBs&sinceMinutes=60
https://cashboard.live/x402/perp-scan?markets=HYPE,SOL&limit=10&conditions=%5B%7B%22metric%22%3A%22funding-apr%22%2C%22direction%22%3A%22above%22%2C%22threshold%22%3A%2250%22%7D%5D

To see the price and the payment requirements without paying, request a route with its arguments and no payment header. A request with no arguments at all is treated as a probe: it gets the 402 for a built-in example call instead of an error about missing arguments, which is what registries and crawlers need to read the requirements.

curl -i "https://cashboard.live/x402/oi-movers?window=60&direction=up&limit=10"

Discovery documents

Two documents describe the paid routes for tools that read them: https://cashboard.live/openapi.json, an OpenAPI description with the price of each route, and https://cashboard.live/.well-known/x402, a list of the five paid resources. Each 402 also carries an input example and the input and output schema of the tool.

Payments are in USDC, which has 6 decimals, so 0.02 is 20000 in the atomic amount a 402 shows. Every requirement says scheme: "exact", the network, the USDC asset, the payout address and a maxTimeoutSeconds of 60. Base is listed first.

Payments are verified and settled by the Coinbase Developer Platform facilitator. The Solana entry needs the fee payer address the facilitator publishes. If Cashboard cannot read it, the 402 offers Base only and never a Solana entry without it. Check the payout address in the 402 you receive against this page before you sign.

A settled call returns its receipt with the result: the PAYMENT-RESPONSE header on the HTTP routes, and _meta["x402/payment-response"] on an MCP call. It names the settlement transaction, the network and the payer, so you can find the transfer on any explorer for that network.

• A receipt marked pending means the facilitator has not yet confirmed the transfer, and the transaction may still land. You get the result, and nothing asks you to pay again for that call. Cashboard re-checks pending payments against the chain every minute.
• If settlement fails, you get a 402 with the error Settlement failed and no data. The tool ran, but its content is withheld until the payment goes through.
• Each signed payment can be used once. The same payment sent twice at once gets 409 or an error that says it is already in use, and only one call runs.

Cashboard runs the tool before it settles, and settles only a complete result. A failed or partial call never reaches the settlement step, so the signed payment is left unused and it lapses on its own. There is nothing to refund in the normal case.

• An error with no usable result says you were not charged: the upstream data could not be read, the tool took longer than its 8 second budget, the payment could not be verified, the result was larger than 256 KB, or the service was too busy to finish the call in time.
• A payment that does not match the requirements, or that fails verification, gets the 402 again with the reason, and nothing is spent.
• A call refused for a limit, a region or a switched-off tool is never charged. All of these checks run before any payment is settled.
• A sample is never charged.

If you believe you were charged for a call that should not have been, write to the support address on the Refunds page with the transaction hash from the receipt. A settled call is refunded only on request, as a manual USDC transfer from Cashboard's wallet.

• A limit answer is an error with the seconds to wait: 429 with Retry-After on the HTTP routes, and retryAfterSeconds on an MCP call.
• Callers in Cuba, Iran, North Korea and Syria are refused on every path, free or paid, and so are callers in Crimea, Sevastopol, Donetsk and Luhansk wherever the region of the connection can be read.
• Open interest changes are computed from Cashboard's own history, which stores one snapshot of every live Hyperliquid main-dex perp each minute for a little over four hours. That is why the windows are 15 minutes, 1 hour and 4 hours.
• Prices and the cache times above can change. The catalog and the 402 always show the current price.

• No boards. The service has no access to any board, widget, note, alert or address in a Cashboard app, on the web or on desktop. It is a separate server from the one inside Cashboard Desktop.
• No account. There is nothing to sign up for, and no API key or email address is asked for.
• No IP address in the ledger. The ledger records, among other things, the tool, the amount, the network, the payer address, the transaction, the status, the time and whether the answer came from cache. It keeps these for 13 months. Payer addresses are public on the chain anyway.
• Rate limits and free samples use a salted hash of the IP address that changes every day, never the address itself.
• The wallets you pass to cashboard_wallet_swaps are used to read those wallets, and their results are cached for 30 seconds. Nothing else is kept about them.
• Cashboard never holds your keys. You sign each payment in your own wallet.

Each result lists its sources in sources, with a link, and the attribution text where a source requires it. Cashboard does not pass on a source's raw feed. It returns its own computed values and, for Hyperliquid, the public per-market fields listed in the table.

Many of the same providers feed the widgets on a board. Data sources and freshness explains how Cashboard treats provider outages, and what each widget shows when one is down.