Skip to main content
Usage on our pricing plans is measured in API Credits. Credit cost varies by product and transport. Public Market Data WebSocket routes do not consume API credits. Authenticated order-book and trade streams use the byte-based model below for organisations enrolled in WebSocket billing. The Trade API and Copytrade API retain their existing pricing.

​
Credit cost by product

MCP requests carry a 10× multiplier. Every call to the MCP Server costs 10 API credits, ten times a Data API request, reflecting the heavier analytics each MCP tool runs. The run_sql query budget is metered separately, by bytes scanned; see MCP rate limits.

​
Authenticated WebSocket credits

The authenticated routes are /stream/polymarket/partner and /stream/predictfun/partner, plus /stream/polymarket/partner/trades. Use a key with stream.read and sign the connection with HMAC. Snapshots, order-book updates and authenticated trade frames consume 1 credit per 100,000 uncompressed UTF-8 payload bytes. For example, 9,414 bytes consume 0.09414 credit. Fractions accumulate across your organisation’s keys and connections; messages are not rounded up individually. Pings, acknowledgements, error messages and idle time consume no credits. A new snapshot requested when reconnecting counts as a new delivery. Your Console’s Billing and Usage pages include this consumption. Reservations for deliveries awaiting confirmation appear separately from used credits. The included allowance is shared with your other metered API products. This rollout uses the included allowance for WebSocket delivery. When it runs out, the stream sends CREDIT_LIMIT_REACHED and closes with code 1008. Upgrade your plan or wait for the allowance to reset before reconnecting. Automatic WebSocket overage spending is not enabled by this rollout. Metering starts prospectively when your organisation is enrolled. Previous traffic is not back-billed. Public /market streams, UMA and Mempool Fills are separate services and do not inherit this order-book byte rate.

​
UMA stream credits

Under unified billing, each delivered UMA data message costs 0.75 API credit, regardless of payload size. For example, 20 delivered messages cost 15 credits. Heartbeats, error frames, connection setup, ticket issuance and idle time are not charged. A successful UMA REST query costs 1 credit per response, not one credit per record in the response. Pending and confirmed updates are separate messages. Filtering or deduplicating messages in your application does not change the messages already delivered to your connection. Multiple connections are metered separately. The message rate applies prospectively from 7 October 2026 to organisations with active unified billing. Existing historical charges and legacy contracts are unchanged. Monthly cost depends on delivered volume and your plan’s included credits; it is not a fixed monthly fee for listening.