Polybuilders aggregates and analyses every participant in the Polymarket Builder Program. This page documents how the data is collected, classified, refreshed, and verified.
Source of truth
All builder identity, attributed on-chain volume, and active-user counts come from Polymarket's public Data API at data-api.polymarket.com/v1/builders/leaderboard. We pull all 380 builders across all four time periods (24h / 7d / 30d / all-time). The official Polymarket-published page exposes only the top 50 by 30-day volume.
Refresh cadence
- Nightly: leaderboard volumes, ranks, active-user counts (GitHub Action runs at 06:00 UTC).
- Weekly: editorial enrichment — categories, tags, founders, funding rounds, descriptions.
- Quarterly: ecosystem-level analysis (State of Builders annual report).
Taxonomy
Every builder has exactly one category — the answer to "what kind of product is this?" — chosen from: Trading Bot, Trading Terminal, Wallet, Exchange, Aggregator, Analytics, AI Agent, Capital, Sports, or Other. Plus zero-to-many tags — cross-cutting attributes describing surface (telegram, discord, mobile, desktop, browser-extension, web), function (copy-trading, sniper, whale-tracking, news-driven, backtesting, arbitrage), domain (sports, politics, crypto-markets), trust (non-custodial, open-source), and pricing (free, paid). Categories never overlap with tags.
Verification tiers
- Editorial-verified: our team manually researched the builder, opened the product surface, confirmed the URL matches the builder identity, and authored or audited the description.
- Polymarket-verified: the official ✓ flag from the Polymarket Data API — the platform's internal review.
- Auto: we discovered a URL via the enrichment pipeline but haven't manually verified it.
- Unverified: builder code with no published product surface.
Funding research
Funding data is cross-referenced across crypto-fundraising trackers (RootData, CryptoRank, ICO Drops, Messari, DefiLlama Raises, Crunchbase, Tracxn), industry press (The Block, CoinDesk, CoinTelegraph, Decrypt, TechCrunch), and project-published announcements (Medium, Mirror, official blogs). Every entry cites at least one primary or secondary source.
Corrections
Email [email protected] with the builder slug and the specific correction (with a public-source URL). We triage within 48 hours.