برنامج مطوري PredictAsiaX

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. 44 tools exposed on mcp.predictasiax.com, 17 public (no auth) and 27 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 PAX_ACCESS_KEY / PAX_TIMESTAMP / PAX_PASSPHRASE / PAX_SIGNATURE), Session Bearer.

Sandbox in 30 seconds

Anonymous, self-serve, no email:

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, which identifies the builder whose interface routed the specific trade and, where applicable, the builder that first attributed the trading user. Attributed trades earn the builder a share of the trading fee. 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

1. Open builders.predictasiax.com and submit a builder application — product description, target users, expected volume.
2. Get approved to Verified and receive a tier-flagged sk_live_* API key.
3. Build against the sandbox tier ($10 max per order, $100 daily notional, mid-price simulated fills).
4. 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.
5. Apply for Genesis (first 20 slots, merit-awarded) or Partner (negotiated) after demonstrating shipped product and traction.