Same tier ladder as the public API
Org-scoped keys follow the public API’s tier ladder —free, developer, enterprise, and mm — with each tier setting your daily spend cap, per-trade cap, and rate limit. For the current limits per tier, see the public API docs:
Authentication
Key format, scopes, and request signing.
Rate limits
Per-tier limits and the rate-limit response headers.
enterprise and mm tiers (custom limits, negotiated terms), contact [email protected].
Scoped keys and webhooks
- Scopes — keys are issued with explicit scopes, so you can hand a reporting integration read-only access while keeping trading capability on a separate key.
- Webhooks — subscribe to HMAC-signed webhooks to react to events in real time instead of polling. See the webhooks overview.
Embed tracking is analytics-only
A common point of confusion, worth being precise about: Revenue share is trade-level: you earn a share of fees on every trade in markets your organization creates, regardless of where the trade originates — the webapp, an embed on any site, or X. Embedding someone else’s market does not earn you revenue share; creating markets does. See Pricing and revenue share. The two work together: embed tracking shows you which placements drive engagement, while trade-level attribution pays you for the markets you own.No-auth option: the Public Embed API
If you only need to display markets — no trading, no org data — the Public Embed API is public, read-only, and requires no API key at all.Next steps
REST API overview
Endpoints, SDKs, and quickstart for the authenticated API.
Analytics and earnings
What the portal shows you without writing any code.