implyra
Prediction market API

Trader intelligence,
in your product.

One API for the traders behind prediction markets: wallet P&L, rankings, positions and funding on Polymarket and Hyperliquid, Kalshi market data, and Kalshi ↔ Polymarket matching. We provide the data and analytics. You build the experience.

Request API accessRead the docs
Implyra API
curl -G "$IMPLYRA_API_URL/leaderboard/global" \ -d sortBy=sharpe -d advanced=true -d limit=2
Response

GET/leaderboard/global

Traders ranked by Sharpe ratio, with P&L, win rate and risk metrics.

Reference

SourcesPolymarketKalshiHyperliquid
100+ REST routesSSE trades + signalsRead-only analytics
What you can build

Trader analytics, built in.

The data behind the features your users need, from a trader’s track record to the markets they trade.

01Trader analytics

Trader profiles & rankings

Help users evaluate traders with P&L, win rate, drawdowns and risk-adjusted metrics. Filter and rank the records that matter to your product.

  • Track records per wallet
  • Risk and drawdown metrics
  • Rankings by window
  • Flags for whales and new wallets
Read the guide
02Portfolios

Portfolio & position analytics

Show what a trader holds, how their exposure changes and the trades behind it. Connect portfolio views to the markets they trade.

  • Open positions
  • Closed trades
  • Exposure history
  • Links to each market
Read the guide
03Discovery

Market & event discovery

Build screeners and event pages with market history, trading activity and filters. Give every position the context of its underlying question.

  • Prices, volume and liquidity
  • Deltas on 8 windows
  • Composable filters and sorts
  • Kalshi ↔ Polymarket matching
Read the guide
04Research

Cohorts & funding relationships

Compare groups of traders by performance or portfolio size. Explore funding sources and shared flows for deeper research.

  • Cohorts by tier
  • Wallet clusters
  • Funding sources
  • Shared flows
Read the guide
Coverage

Three venues, one schema.

Most prediction market APIs sell prices, order books and trades. Implyra adds what is computed across every wallet, on the same routes the terminal runs on.

Coverage notes
  • Trader rankingsPolymarket/leaderboard/globalHyperliquid/hyperliquid/leaderboard
  • Wallet profiles and P&L historyPolymarket/users/{address}/pnl-historyHyperliquid/hyperliquid/users/{address}/pnl-history
  • Positions, trades and fillsPolymarket/users/{address}/positionsHyperliquid/hyperliquid/users/{address}/fills
  • Holders, whales and smart money per marketPolymarket/markets/{slug}/whalesHyperliquid/hyperliquid/outcomes/{id}/whales
  • Cohorts by P&L tier and sizePolymarket/cohorts/{type}/{tier}Hyperliquid/hyperliquid/cohorts
  • Wallet clusters and similar walletsPolymarket/wallets/{address}/similarHyperliquid/hyperliquid/clusters/{id}
  • USDC funding traces on PolygonPolymarket/funding/trace/{address}
  • Market discovery and searchPolymarketPOST /markets/discoverHyperliquid/hyperliquid/outcomes/discoverKalshi/kalshi/markets
  • Trades, order books and candlesPolymarket/markets/{slug}/tradesHyperliquid/hyperliquid/outcomes/{id}/tradesKalshi/kalshi/markets/{ticker}/orderbook
  • Kalshi ↔ Polymarket matchingPolymarket/cross-platform/matchesKalshi/cross-platform/arbitrage

One example route per venue from the OpenAPI 3.0 contract. Fields and history vary by venue and dataset; each reference page states its coverage.

A request, then a product

Start with the data.

Choose a feature, set its parameters and copy a request you can run from your server.

Request builder

Evaluate a track record with performance and risk metrics together. Historical results describe the record, not the next trade.

Full reference
GET/leaderboard/global
Terminal
curl --fail-with-body \  "${IMPLYRA_API_URL%/}/leaderboard/global?limit=20&offset=0&advanced=true&sortBy=pnl&sortOrder=DESC" \  -H "Accept: application/json"
rows[].overallPnl
Realized + unrealized P&L in USD.
rows[].advanced
Risk metrics when available; preserve nulls.
nextCursor
Continue with the returned cursor.
Example only · No request is sent from this page.

Set IMPLYRA_API_URL to your assigned REST base URL and apply the access configuration supplied during onboarding.

Integration

Tell us what you’re building.

Tell us which features you need. We’ll help you choose the data, coverage and access that fit.

  1. 01

    The data

    Which venues, records and historical periods does your product need?

  2. 02

    The workload

    How will you query the API, and which streams would you use?

  3. 03

    The access

    Get your endpoints, access configuration and examples for your integration.

Discuss your integrationExplore the terminal
FAQ

Before you build.

  • Venue APIs serve markets, order books, trades and individual accounts. Implyra adds what is computed across every wallet: rankings with risk metrics, P&L history, holders, whales and smart money per market, cohorts, clusters and funding traces, plus Kalshi ↔ Polymarket matching, in one documented schema.
  • The research dashboard is free. API access is arranged separately and quoted around your data requirements, request volume and integration support.
  • Each venue has its own endpoints and coverage. Wallet analytics cover Polymarket and Hyperliquid; Kalshi does not publish who trades, so its endpoints are market-level. Indexed history starts at Polymarket order-book fills from November 2022, Kalshi trades from March 2026, and Hyperliquid perps and HIP-4 outcomes from May 2026. Cross-venue matching covers Polymarket and Kalshi. Matches can be empty, and a returned history may be partial. We confirm the fields and periods your application needs during onboarding.
  • Use the REST base URL and deployment access instructions supplied during onboarding. Keep credentials on your server. The request builder generates examples locally; the endpoint reference explains parameters, pagination and response fields.
  • REST and SSE run on separate services. Available channels and connection access are agreed during onboarding. Some wallet streams require an authenticated session or a short-lived ticket; the streaming guide documents those requirements.