The PredictAsiaX Builder Program has three tiers — Verified (default on approval), Genesis (first 20 slots, merit-awarded, 10× rate limits), Partner (individually negotiated, up to 20×). Grants pay in PAX with cliff-plus-linear vesting across three tracks (Hackathon 500–2,000, Builder 5,000–50,000, Partner 100,000–500,000) capped at 2M / 5M / 15M PAX per month / quarter / year. The API surface is 38 REST paths across 14 tag groups plus a WebSocket stream with 48 event types plus a 7-tool MCP server. Sandbox is anonymous, self-serve, on the production host with $10 / $100 caps and a 30-day key.
Who the Builder Program is for
The PredictAsiaX Builder Program serves developers, agents, market-making desks, and interface builders who want to route real prediction-market flow through their own product and be paid for it. If you are building a trading bot, an AI agent, a mobile front-end, an analytics dashboard, or an on-ramp that lets your users trade on PredictAsiaX, the Builder Program is where you get an API key, attribution, and a path to grants.
Three tiers, one promotion path
Every approved builder starts at Verified. Two higher tiers are earned or negotiated:
Verified— default on approval. Full API access, base rate limits, PAX grant eligible.
Genesis— first 20 slots, merit-awarded. 10× base rate limits (custom bursts negotiable), featured placement on the /builders directory with verified badge, early access to unreleased APIs, engineering direct channel with weekly office hours, expanded grant range.
Partner— individually negotiated for exchanges routing flow, market makers, and mainstream integrations. Up to 20× rate limits (fully negotiable per contract), dedicated account channel, co-marketing, fee-tier discount, and the largest grant range.
Tier promotion is based on shipped product and traction, not on payment. Genesis and Partner are earned by demonstrating live users and real volume through your integration.
The PAX grant program
Grants are paid in PAX, the platform's native token, with cliff-plus-linear vesting. Pull-claim semantics — vested tokens sit on the platform until you call claim() to move them into custody.
Hackathon — 500–2,000 PAX.Weekend hackathon winners, first integrations, small experiments. No cliff · roughly 6 months linear vest · 48-hour decision · public GitHub and demo required.
Builder — 5,000–50,000 PAX.Independent developers shipping a real product on PredictAsiaX. 3-month cliff · 12-month linear vest · weekly cohort · requires a live URL with more than 30 days of uptime and either ≥100 users or $10,000 in routed volume.
Partner — 100,000–500,000 PAX.Exchanges routing flow, market makers, and mainstream integrations. 6-month cliff · 24-month linear vest · four milestone gates at 25 % each · monthly cohort · co-marketing and dedicated channel.
Budget caps enforced: 2M PAX per month, 5M per quarter, 15M per year. Applications beyond the cap return GRANT_BUDGET_EXCEEDED immediately. Current usage is queryable through the admin grants budget endpoint.
The API surface, at a glance
REST.38 paths and 42 operations across 14 tag groups: Discovery, Builders, Apps, Attribution, Revenue, Connect, Subaccounts, Composer, Liquidity, Data, Webhooks, Marketplace, Oracle, Sandbox. Envelope response format, Money always a decimal string, deterministic market IDs of the form m_.
WebSocket.A single multiplexed connection carrying 48 event types across market data, fast round, account, security, and ops. Subscribe with method SUBSCRIBE and a list of channels.
MCP.Seven tools exposed on mcp.predictasiax.com, four read-only (no auth) and three that require an API key. See verifiable settlement for the audit endpoints and Merkle inclusion flow.
Auth.Three schemes: API Key (sk_live_* via X-Api-Key), HMAC (four headers POLY_ACCESS_KEY / POLY_TIMESTAMP / POLY_PASSPHRASE / POLY_SIGNATURE), Session Bearer.
Sandbox in 30 seconds
Anonymous, self-serve, no email:
{`curl -X POST https://api.predictasiax.com/v1/sandbox-keys
# → { "api_key": "sk_live_...", "tier": "self_serve",
# "limits": { "max_order_usdt": 10, "daily_notional_usdt": 100 },
# "expires_at": "…30 days from now…" }`}
Same production host, fills simulated at mid-price, capped at $10 per order and $100 daily notional, key valid for 30 days. Five-minute walkthrough: mint → list markets → place a $1 order → read the resulting fee split → cancel.
Attribution and payouts
Attribution is captured in the signed order intent — the execution_builder_id field identifies the builder whose interface routed the specific trade, and, where applicable, acquisition_builder_id identifies the builder that first attributed the trading user. Attributed trades participate in the fee split; the taker fee is 50 bps of notional. Payouts are held for anti-abuse review and then batched in USDT to the wallet address you register in the Builder Portal.
How to apply
Open builders.predictasiax.com and submit a builder application — product description, target users, expected volume.
Get approved to Verified and receive a tier-flagged sk_live_* API key.
Build against the sandbox tier ($10 max per order, $100 daily notional, mid-price simulated fills).
Ship to production. Every fill writes an attributed record to the shared ledger; payouts batch to your registered USDT address after the anti-abuse hold.
Apply for Genesis (first 20 slots, merit-awarded) or Partner (negotiated) after demonstrating shipped product and traction.
PAX Holder Graduation Discount
Long-term PAX holders climb Builder tiers with a discounted graduation deposit. The discount scales with your PAX Holder tier (30-day rolling USD × continuous-days-held).
Bronze ($100 for 7 days) — −10% off graduation threshold
Silver ($500 for 30 days) — −20% off
Gold ($5,000 for 90 days) — −30% off
Platinum ($50,000 for 180 days) — −50% off
Diamond ($500,000 for 365 days) — −70% off
The discount is applied automatically by the tier graduation cron. Track your progress at the Tier Center.
Frequently asked questions
What is the PredictAsiaX Builder Program?
The Builder Program is how third-party developers, agents, and integration partners build on top of PredictAsiaX. It provides an API surface (38 REST paths across 14 tag groups plus a WebSocket stream with 48 event types), attribution for trades routed through your interface, a PAX-denominated grant program, and a three-tier commercial structure (Verified / Genesis / Partner) with progressive benefits.
What are the three builder tiers?
Verified is the default tier every approved builder starts at, with base rate limits and standard API access. Genesis is a merit-awarded tier capped at the first 20 slots, with 10× rate limits, featured placement on the /builders directory, early access to unreleased APIs, and an expanded grant range. Partner is individually negotiated for high-flow integrations, exchanges, and market makers, with up to 20× rate limits, dedicated account channels, co-marketing, and the largest grant range. Full tier detail is on builders.predictasiax.com and docs.predictasiax.com/builders.
How does the PAX grant program work?
Grants are paid in PAX, the platform's native token, with cliff-plus-linear vesting. Three tracks: Hackathon (500–2,000 PAX, no cliff, roughly 6-month linear vest, 48-hour decision, public GitHub and demo required), Builder (5,000–50,000 PAX, 3-month cliff and 12-month linear vest, weekly cohort, requires a live URL with >30 days uptime and either ≥100 users or $10,000 in routed volume), and Partner (100,000–500,000 PAX, 6-month cliff and 24-month linear vest, four milestone gates at 25 % each, monthly cohort). Budget caps are 2M PAX per month, 5M per quarter, 15M per year — applications beyond the cap return GRANT_BUDGET_EXCEEDED.
How do I authenticate against the API?
Three authentication schemes are supported. (1) API Key — mint a key from Settings → API Keys or from POST /v1/sandbox-keys, then send it in the X-Api-Key header. All keys are sk_live_* prefixed; sandbox is differentiated by tier=self_serve on the key, not by the prefix. (2) HMAC — sign requests with four headers named POLY_ACCESS_KEY, POLY_TIMESTAMP, POLY_PASSPHRASE, and POLY_SIGNATURE, where signature = base64(HMAC-SHA256(secret, timestamp + method + path + body)). (3) Session Bearer for interactive apps that hold a user session. Full detail in the docs authentication guide.
How does the sandbox work?
Anonymous, self-serve, no email required. POST to /v1/sandbox-keys and receive a sk_live_* key at tier=self_serve. The sandbox is on the same production host — no separate URL — with fills simulated at mid-price. Per-key caps: $10 max per order, $100 daily notional, key valid for 30 days. A full curl walkthrough (mint → list markets → place a $1 order → read the fee split → cancel) takes about 5 minutes.
What API surface is available?
38 REST paths and 42 operations across 14 tag groups: Discovery, Builders, Apps, Attribution, Revenue, Connect, Subaccounts, Composer, Liquidity, Data, Webhooks, Marketplace, Oracle, and Sandbox. Plus a WebSocket API with a single multiplexed connection and 48 event types across market data, fast round, account, security, and ops. Design principles: envelope response format, Money as a decimal string, deterministic market IDs (m_<sha256[0:16]>), and X-PII-Redacted header always present.
What is the MCP integration?
mcp.predictasiax.com exposes a Model Context Protocol server with 7 tools that AI assistants (Claude Desktop, Claude Code, and any MCP-compatible client) can invoke directly. Read-only tools work without authentication: pax.market_search, pax.probability_movers, pax.resolution_evidence, pax.sandbox_agent_examples. Write and account tools require an API key: pax.portfolio_read, pax.place_order, pax.cancel_order. Full tool schemas are at mcp.predictasiax.com/mcp/manifest.json.
How is trade attribution earned?
Attribution is captured in the signed order intent — the execution_builder_id and (where applicable) acquisition_builder_id fields identify which builder routed the trade. Attributed trades participate in the fee split, and settled attribution flows into the financial event ledger visible to the builder via the Builder Portal (builders.predictasiax.com). The taker fee is 50 bps of notional. Payouts are held for anti-abuse review and then batched to your registered USDT address.
How do I move from sandbox to production?
Apply via builders.predictasiax.com to the Verified tier. Once approved you receive a tier-flagged sk_live_* production API key. The same endpoints, same schemas, and same auth work — only the tier flag on the key changes. From Verified you can build up eligibility for Genesis (first 20 slots, merit-awarded on shipped product and traction) or Partner (individually negotiated).
