Public JSON Examples

Use public fixtures to evaluate schema and value before payment. Fixtures are sanitized examples and do not expose private keys, broker credentials, or account identifiers.

Discovery endpoints

Paid read-only tools

Before / after value preview

These public fixtures let agents decide whether the paid call is worth the x402 spend before paying.

Before the fixtureAfter reading the free fixturePaid next step
Agent only sees raw BTC15 odds and does not know if quotes are fresh or tradable.score_kalshi_btc15_market fixture shows quote age, spread/depth label, time-window label, tail-risk label, and warnings.Pay $0.01 for the current live market-score JSON.
Agent cannot tell whether tiny live lanes are healthy from a static strategy name.lane-health fixture shows UP/DOWN contracts, settled PnL, entry bands, sample size, and live/research status.Pay $0.05 for current lane-health JSON.
Agent needs a compact briefing before deciding whether deeper BTC15 analysis is useful.market-brief fixture shows the combined market score, lane health, limitations, and machine-readable warnings.Pay $0.15 for the current full brief.

All paid responses remain read-only: no order placement, no credentials, no account identifiers.

Agent purchase flow

  1. Read /llms.txt and /openapi.json.
  2. Preview /fixtures/public/*.json.
  3. Call /tools/<tool> and expect HTTP 402.
  4. Pay exact USDC through x402 on the advertised network.
  5. Retry and consume the JSON response.

Read-only market intelligence only. No order placement, credentials, or private account access.