
Build typed Polymarket apps with public reads, resumable scans, real-time topics and separate authenticated actions.
- Language TypeScript · JavaScript
Explore a workflow
Start with the data or action your application needs, then choose a compatible interface and access model. This family covers building blocks for research applications, data systems and trading integrations.
Compare programming languages, runtime and deployment requirements, API coverage and entitlements. A repository can supply code without granting access to a hosted dataset. Read the relevant software and data licensing terms.
Separate public research reads from account operations. Establish the credentials and permissions needed for each action before enabling them in your application or agent. Move to infrastructure tools when the main task is running the service rather than choosing its data interface.

Build typed Polymarket apps with public reads, resumable scans, real-time topics and separate authenticated actions.

Query and stream decoded trades, token balances and settlement events.

Public wallet checks with explicit coverage, historical diagnostics and paid monitoring or reconciled reads.

Retrieve recorded book ladders, sports mappings and aligned price bars for research and replay.

Query blockchain activity with SQL and publish dashboards for volumes, wallets, fills and custom research.

Economic-data search and history for checking the precise measure behind a macro contract.

Structured news events and knowledge-graph data for reproducible research and media monitoring.

Replicate fills, positions and balances for custom analytics, applications and alerts.

Trade defined event outcomes, inspect order-book depth and resolution rules, and connect through web, mobile or the exchange API.

Research tennis with scores, fixtures, history and odds; advanced delivery and model fields depend on the plan.

Bring sports schedules, odds and supported fair-price analysis into an application or research agent.

Export Polymarket history and replay Python strategies with stated latency, queue and fill assumptions.