PredictionToolkit
What is PMXT hosted API?
Router provides one search across the hosted catalog. Matching results include relation types and confidence scores, so inspect the underlying contracts before treating a cluster as equivalent outcomes. The shared Event, Market and Outcome schema helps carry that identity into an application.
Hosted operation differs from running pmxt-core locally with venue-native access. In particular, the documented hosted write path uses PreFundedEscrow custody. Method coverage depends on both venue and runtime mode; catalog IDs do not always substitute for venue-native IDs.
Who it is for
- Multi-venue research applications.
- Teams using hosted catalog and matching infrastructure.
- Developers combining discovery with supported execution.
Features and coverage
- Shared market objects
Use Event, Market and Outcome across venue clients.
- Router search
Search the hosted catalog with one query.
- Matched clusters
Inspect related markets, relation types and confidence.
- Hosted history
Access candles and order-book snapshots under the applicable plan.
- Venue methods
Query markets, read positions and create orders where implemented.
- Hosted writes
The documented trading path uses PreFundedEscrow.
- Python and TypeScript
Choose Python pmxt or TypeScript pmxtjs.
Workflows with PMXT hosted API
Compare an event
Search with Router, retain cluster relation and confidence, then inspect bid/ask data and contract rules before choosing a venue client.
Scope an integration
Start with a small read request, budget REST and WebSocket usage, then follow the hosted trading quickstart for account writes.
Pricing and total cost
Hosted data is metered in credits: Free, Starter US$29.99/month and Pro US$99.99/month.
Free
US$0/month
- 25,000 credits/month; 60 requests/minute; 5 WebSocket streams.
Starter
US$29.99/month
- 250,000 credits/month; 300 requests/minute; 20 streams.
Pro
US$99.99/month
- 1 million credits/month; 1,000 requests/minute; 100 streams.
Fees and usage costs
- One REST call costs 1 credit; one WebSocket message costs 0.1 credits.
- Published plans are personal-use only; enterprise access is quoted separately.
Getting started
Before you start: Hosted and self-hosted credentials and custody differ.
- Create a hosted API key and install pmxt or pmxtjs.
- Initialize Router or a venue client and inspect a small market response.
- Check matching and venue support, then follow the hosted trading guide if adding execution.
Hosted writes use a different custody and credential model from self-hosting.
Useful links
What to check
- Hosted and self-hosted credentials and custody differ.
- Catalog IDs and native venue IDs are not always interchangeable.
- Shared method names do not imply universal venue support.
- Published data plans permit personal use only.
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.
Related tools
Browse category
Use one Python or TypeScript interface across supported prediction venues, with an explicit hosted or local backend choice.
- Language Python · TypeScript
Query markets, books, trades, price history and standardized sports data through one REST interface.
- Access API · MCP
An MCP bridge to PMXT data and supported account methods, using your chosen hosted or local backend.
- Access MCP
Guides and workflows
Frequently asked questions about PMXT hosted API
How does hosted mode differ?
It uses PMXT infrastructure and a key; local mode runs pmxt-core with venue-native access.
What consumes credits?
A REST call uses 1 credit; a WebSocket message uses 0.1 credits.
Does matching prove equal settlement terms?
No. Inspect relation types, confidence and the contracts themselves.