Auspex
…

API

The same data the screener uses, exposed as plain JSON. No auth, no rate limits beyond Vercel's defaults. Endpoints are served with a 60–300 s edge cache so repeated calls are cheap.

GET/api/marketsOpen live JSON

All crypto-vertical Polymarket markets, sorted by 24-hour volume descending. Snapshot refreshed every ~4 hours by a cron pipeline (live prices are overlaid per-request) and cached at the edge for 60 s.

Query parameters
family
string

Filter to a single market family — one of binance_price, holdings_event, fdv_after_launch, polymarket_team_judgment.

limit
number

Max rows returned (1–5000, default 500).

Example request
curl -s 'https://auspex.to/api/markets?family=binance_price&limit=10' | python3 -m json.tool
Example response
{
  "generatedAt": "2026-05-19T12:40:28.204Z",
  "total": 157,
  "returned": 10,
  "markets": [
    {
      "id": "573655",
      "question": "Will Bitcoin hit $150k by June 30, 2026?",
      "slug": "will-bitcoin-hit-150k-by-june-30-2026",
      "family": "binance_price",
      "source": "binance",
      "pair": "BTC/USDT",
      "tokenYes": "139156…",
      "tokenNo": "138269…",
      "tickSize": 0.001,
      "negRisk": false,
      "impliedYes": 0.0135,
      "bestBid": 0.013, "bestAsk": 0.014,
      "currentValue": 76749.49,
      "thresholdValue": 150000,
      "distancePct": 4.488336733,
      "alreadyTriggered": false,
      "liveState": "live",
      "rc": 44.7,
      "endDate": "2026-07-01T04:00:00Z",
      "volumeTotal": 15734008,
      "volume24h": 5821652,
      "liquidity": 19822.55
    },
    "…"
  ]
}
GET/api/markets/by-tokenOpen live JSON

Resolve one or more CLOB token IDs back to the market that owns them. Useful for clients that index trades on-chain by token-id and need to join back to the human question.

Query parameters
ids
string

Comma-separated list of CLOB token IDs (uint256 strings). Max 500 per request.

Also accepts POST with body { "tokens": ["…", "…"] } — same response shape. Use POST when your token list exceeds the URL length limit (~8 KB on most CDN edges).

Example request
curl -s 'https://auspex.to/api/markets/by-token?ids=139156…,138269…' | python3 -m json.tool
Example response
{
  "count": 2,
  "lookup": {
    "139156…": {
      "marketId": "573655",
      "question": "Will Bitcoin hit $150k by June 30, 2026?",
      "outcome": "yes",
      "slug": "will-bitcoin-hit-150k-by-june-30-2026"
    },
    "138269…": {
      "marketId": "573655",
      "question": "Will Bitcoin hit $150k by June 30, 2026?",
      "outcome": "no",
      "slug": "will-bitcoin-hit-150k-by-june-30-2026"
    }
  }
}
GET/api/find-proxyOpen live JSON

Resolve a Polygon address to or from its Polymarket DepositWallet proxy. Powered by Etherscan V2 log queries against the OZ OwnershipTransferred event emitted on proxy deployment. Requires POLYGONSCAN_API_KEY on the deployment; returns 503 otherwise.

Query parameters
eoa
0x-address

Forward lookup: given a wallet EOA, return the most-recently-deployed Polymarket proxy that EOA owns. Returns proxy: null when no proxy is found.

proxy
0x-address

Reverse lookup: given a candidate proxy address, return the list of EOAs that appear in its initial-owners array. Use this to verify whether a wallet is authorized to sign for a given proxy.

Auspex's onboarding flow uses both modes: the forward lookup auto-discovers a connecting wallet's Polymarket account; the reverse lookup validates that a pasted proxy is actually owned by the connecting wallet (catching the otherwise-silent "balance reads 0" failure mode).

Example request
curl -s 'https://auspex.to/api/find-proxy?eoa=0x1111111111111111111111111111111111111111' | python3 -m json.tool
Example response
{
  "proxy": "0x2222222222222222222222222222222222222222",
  "count": 1,
  "factory": "0xd3447596d282d62bc94240d17caee437efcfde62"
}
GET/api/healthOpen live JSON

Liveness probe. Reports whether the snapshot file is loadable and how stale it is. Anything over 43200 s (12 h) of snapshotAgeSeconds indicates the cron pipeline has fallen behind (the endpoint returns 503 past that threshold).

Example request
curl -s 'https://auspex.to/api/health' | python3 -m json.tool
Example response
{
  "status": "ok",
  "snapshotAt": "2026-05-19T12:40:28.204Z",
  "snapshotAgeSeconds": 352,
  "markets": 345,
  "elapsedMs": 22
}

Caching + freshness

Markets data is refreshed server-side every ~4 hours by a GitHub Actions cron (see .github/workflows/data-refresh.yml). The pipeline pulls fresh prices from Binance (CryptoCompare fallback for geo-blocked runners), recomputes resolution- confidence scores, and commits the new snapshot, which triggers a Vercel redeploy. Each API response carries an HTTP Cache-Control header so the edge holds it for the cache window even between snapshot pushes.

Stability & attribution

These endpoints are stable but not formally versioned — fields may be added; existing field names and types won't change without a deprecation note in /changelog.

The data is a presentation layer over publicly available Polymarket Gamma + CLOB sources, plus market-resolution-source prices (Binance, CryptoCompare). Use it freely. If you ship something cool with it, a link back to auspex.to is appreciated but not required.