Prediction-market data your agent can buy itself.

Option 1 · MCP

One line in Claude, Cursor, or Windsurf

All ten endpoints as MCP tools. Your wallet key stays on your machine and is never sent anywhere. Before signing any payment the server checks that the recipient is OyaPicks, the amount is at or under $0.30, and the network is Base. The address is a constant in the source, not read from the response, so a redirected endpoint cannot point payments elsewhere.

{
  "mcpServers": {
    "oyapicks": {
      "command": "npx",
      "args": ["-y", "oyapicks-mcp"],
      "env": {
        "OYAPICKS_WALLET_PRIVATE_KEY": "0xyourkey"
      }
    }
  }
}

View on npm →Read the source, it is one file →

Option 2 · Direct HTTP

Plain requests, paid on the 402

Every endpoint is a GET that returns JSON. Call it, get a 402 with the payment terms, sign, retry. Any x402 client library handles this for you.

Step 1 · you ask, we quote

$ curl -i "https://oyapicks.app/api/x402/single-market?q=world+cup"

HTTP/2 402
PAYMENT-REQUIRED: <base64 payment terms>

# Decoded, the terms say: $0.01 USDC, network eip155:8453,
# payTo 0x7df9C5eDBf039b1C645d7697F58EfD143f0986E1

Step 2 · you pay, we answer

# Your x402 client signs those terms and repeats the request
# with a PAYMENT-SIGNATURE header. That call returns 200:

{
  "product": "oyapicks-single-market",
  "query": "world cup",
  "found": true,
  "market": {
    "question": "...",
    "venue": "polymarket",
    "impliedProbability": 0.555,
    "impliedProbabilityPct": 56,
    "volume24hUsd": 109556.5,
    "endDate": "2026-08-08T15:00:00Z"
  }
}

Endpoints

Eleven products, two rails

Paths below are the Base routes. For Algorand, append -algo to any path. The data is identical. One exception: alpha-book is Algorand only, takes no suffix, and has no Base route.

Payment

Where the money goes