Polytoolhub
What is Dome?
Dome’s documentation announces that all hosted APIs reached end of life on April 28, 2026, following its acquisition by Polymarket. Its historical API and SDK references remain useful for understanding an existing integration. They cover Polymarket and Kalshi data, wallet analytics, order-book history and matching markets. The provider directs developers toward the new Polymarket APIs; a cross-venue application also needs a replacement for its Kalshi path.
Who it is for
- Developers maintaining an existing Dome integration
- Teams mapping legacy endpoint calls to a replacement
- Researchers identifying the provenance of previously collected Dome data
Features and coverage
- Available on
- API, TypeScript, Python, WebSocket
- Markets & venues
- Polymarket, Kalshi
- Research topics
- Historical data, Live market data
- Legacy venue normalization
Dome standardized Polymarket and Kalshi market data behind one API; existing integrations must replace that provider layer.
- Historical-data migration
The old interface covered price history, trades and order-book data. Map the records your application actually consumed to a replacement source.
- Streaming migration
Clients using the old real-time feed need a replacement connection and subscription format.
- Market-ID mapping
Preserve native venue identifiers from existing stored records when changing providers.
- Retirement notice
The provider documentation states that all Dome APIs reached end of life after its acquisition by Polymarket.
Workflows with Dome
Audit an existing integration
List the Dome endpoints, fields and stream messages used by your application. Separate market discovery, historical research and execution so each can be replaced with an appropriate provider.
Migrate stored identifiers
Retain native venue IDs and timestamps from the existing database; compare a sample of events, outcomes and prices after introducing the replacement.
Choose a replacement
Use native Polymarket or Kalshi documentation for venue-specific integration, or compare current multi-venue data providers if a common schema is necessary.
Pricing and total cost
The hosted API service is discontinued. The public SDK and API references are retained for migration research; use the replacement provider’s pricing for new work.
Getting started
Before you start: Hosted APIs have a provider-announced end-of-life date that has passed; do not use the homepage’s older signup prompt as evidence of ongoing access.
- Inventory existing Dome calls and SDK methods in your application.
- Separate market metadata, trades, wallet analytics, order-book history, matching and streaming dependencies.
- Map the Polymarket paths to the replacement APIs linked by the provider.
- Choose a separate supported source for Kalshi and any historical data absent from the replacement.
- Compare identifiers, timestamps, pagination and outcome labels against a saved sample before switching the integration.
Useful links
What to check
- Hosted APIs have a provider-announced end-of-life date that has passed; do not use the homepage’s older signup prompt as evidence of ongoing access.
- An available SDK package does not imply an available hosted backend.
- Polymarket’s replacement API link does not by itself replace Dome’s Kalshi coverage or historical retention.
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 Dome?
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 category
Query normalized Polymarket and Kalshi markets, historical books, wallet analytics and matched events through one data API.
- Data coverage Markets · Events · Order books · Trades · Prices · Positions · Cross-venue matches
- Access API
Access normalized prediction-market listings, trades, quotes, order books and historical candles through REST, JSON-RPC or MCP.
- Data coverage Markets · Trades · Prices · Order books
- Access API · MCP
Use Python or TypeScript clients with a common prediction-market interface, targeting hosted PMXT or a locally run backend.
- Language Python · TypeScript
Frequently asked questions about Dome
Can I start a new Dome API integration?
The documentation announces end of life for all hosted APIs and directs users to replacement Polymarket APIs.
Why keep this card?
Existing applications and datasets may still reference Dome methods, identifiers and schemas.
Does installing the SDK restore service?
No. A client package and its hosted API backend are separate dependencies.
What needs extra attention during migration?
Kalshi coverage, historical order books, market matching and streaming may require separate replacements.