What is Struct Polymarket Explorer repository?
Polymarket Explorer is the public application source behind a Struct-powered analytics experience. It contains a substantial frontend and server-rendered page model for traders, markets, events and builders. Struct has sunset its Polymarket service, so the repository is useful as an application reference with a data-adapter migration requirement.
Who it is for
- Developers building an analytics frontend
- Teams studying trader and market page architecture
- Existing users planning to replace the Struct data layer
Features and coverage
- Available on
- Next.js, TypeScript, React
- Markets & venues
- Polymarket
- Trader profiles
P&L charts, daily heatmaps, positions, activity and performance summaries.
- Trader DNA
A radar-style presentation derived from lifetime trading statistics.
- Market and event pages
Probability charts, holders, trades and related markets.
- Builder analytics
Fee history, retention and side-by-side comparisons.
- Global dashboard
Volume, trade count, fees and trader activity views.
- Search and sharing
Command-palette navigation and chart export as PNG.
- Server-side data access
Keep the provider key on the server and deduplicate requests during rendering.
Workflows with Struct Polymarket Explorer repository
Reuse the page architecture
Inspect the trader, market and event routes, then map their data needs to a current provider.
Migrate a Struct installation
Replace the SDK-backed calls, reconcile P&L definitions and verify each chart against the new response shapes.
Build a shareable research view
Adapt the chart and image-export components while preserving the provenance of the displayed data.
Pricing and total cost
The repository has no listed hosted subscription. Hosting and replacement data-provider access are separate; the original Struct Polymarket service is discontinued.
Getting started
Before you start: The README’s Struct API-key prerequisite no longer establishes a working data service.
- Inspect the source and its server-side Struct SDK calls.
- Choose a current data provider before planning a live deployment.
- Use the documented Node.js and pnpm environment.
- Map the required models and identifiers.
- Adapt the data layer and verify P&L and activity calculations.
- Configure authentication and analytics services only if needed.
Useful links
What to check
- The README’s Struct API-key prerequisite no longer establishes a working data service.
- A missing key renders a setup state rather than live analytics.
- Authentication defaults and allowed origins require adaptation outside the original deployment.
- Public source code does not itself grant access to its former backend.
A closer look
Ratings & reviews
User reviews 0
The main score switches to user ratings after 5 published reviews.
A specific example helps the next person choose the right tool.
Write a review
How was your experience with Struct Polymarket Explorer repository?
Share what you used, what worked and what could be better. We confirm your email and review the submission before publishing.
To submit a review, email info@polytradingbot.com with the tool name, your rating and your experience. Enable JavaScript to prepare a draft here.
Related tools
Browse categoryFrequently asked questions about Struct Polymarket Explorer repository
Can I deploy it and immediately get live data?
The original Struct data dependency needs a current replacement.
Is this the same product as Struct’s hosted API?
It is the application repository that consumed that API.
Where is the API key used?
Data fetching happens server-side.
Which parts are useful for a new project?
The route structure, trader views, chart components, tables and image-sharing flow.


