Skip to main content
The Data API’s core analytics surface is live on Predict.fun. Every figure is derived from on-chain BNB Chain settlement records replayed through the same share-level FIFO cost-basis engine as Polymarket, and reconciled against the venue’s own API. Predict.fun endpoints live under the /predict/ path segment:
Your partner account needs the predictfun venue enabled (in addition to the analytics.read scope) — otherwise requests return 403 VENUE_NOT_ENABLED. Check your organisation’s product access in the Console. Contact the team if the venue is not enabled.
Addresses are BNB Chain 0x… addresses (Kernel smart accounts or EOAs), matched case-insensitively.

​
What you can query

Same shapes, parameters, and numeric conventions as the Polymarket routes.

​
Venue differences

  • Realized PnL is already net of fees. Predict.fun charges fees in the proceeds asset, so ?basis=net and ?basis=gross return the same number; fee fields are informational.
  • Activity types are limited to the on-chain lifecycle set: TRADE, REDEEM, SPLIT, MERGE, CONVERSION. Off-chain income and transfer types (rewards, rebates, deposits, withdrawals) don’t exist on this venue.
  • Categories come from Predict.fun’s own tag tree, not Polymarket’s.
  • Field names keep the _usdc suffix for shape parity; amounts are in the venue’s USD-stable collateral.

​
Not available on this venue

Tax statements and the PMWAS accounting surface (/statements, /metrics, /reconciliation, /tax-report, /event-graph, /entity), /combo-markets, and /usdc-balance are Polymarket-only today. These return an explicit 404 with {"error": "not available for this venue", …} — never an empty success.