Polymarket Builder Program: Overview for Developers

The Polymarket Builder Program is a way for third-party operators to route orders through the Polymarket CLOB with attribution, earn builder fees in basis points, and access program benefits like higher relayer limits and rewards. This guide explains how the program works, the three tiers, how revenue share works in principle, and practical integration notes for engineering teams using the Polymarket Relayer Client.

Key takeaways

• The Builder Program lets third parties route orders through the CLOB with attribution and earn builder fees in basis points.
• There are three tiers (Unverified, Verified, Partner) with increasing daily relayer limits and rewards.
• Builder integration is done via attribution headers and the Polymarket Relayer Client SDK (TypeScript and Python) handles wallet deployment, approvals, CTF ops, and order placement.
• Maker fees on Polymarket are zero; builder fees are paid to builders at execution and expressed in basis points.
• Credentialing and builder settings are managed at polymarket.com/settings; revenue details and exact fee rates are controlled by Polymarket and may change.

Why the Builder Program exists

Polymarket runs a Central Limit Order Book (CLOB) and sponsors gas through a Relayer. The Builder Program provides a formal way for third parties to add order flow to that CLOB while receiving attribution and a revenue share (builder fees). For developers building routing logic, market-making front ends, or trading infrastructure, the program creates a direct, supported path to send flow into Polymarket's exchange.

Program tiers and what they mean

H2: The three tiers

• Unverified
  • Daily relayer limit: 100 orders per day.
  • Benefits: Gasless trading and attribution only.
• Verified
  • Daily relayer limit: 10,000 orders per day.
  • Benefits: Weekly USDC rewards based on volume plus builder fees earned in basis points.
• Partner
  • Daily relayer limit: Unlimited.
  • Benefits: Highest rate limits and elevated support; access to the highest reward tiers.

These are Polymarket's published tier rules. Tiers affect the program's rate limits, reward eligibility, and support level; they do not change the basic mechanics of how builder fees are applied at trade execution.

How builder fees and attribution work

Builder fees are configured as basis points on routed orders and are paid out to the builder when an order executes. Attribution is implemented via headers that identify the routing builder; the Relayer uses those headers to credit the appropriate builder on execution.

Important mechanics to remember:

• Fees are expressed in basis points and applied at execution; maker fees on Polymarket remain zero.
• Attribution headers are required for a trade to be credited to a builder. The Relayer and CLOB expect those headers in the request.
• Builder rewards for Verified builders include weekly USDC payments based on volume plus the accumulated builder fees; Partner tier has elevated rewards and support.

Polymarket controls the exact fee rates and reward formulas. Builders should not assume fixed rates; check polymarket.com/settings for current credentialing and builder configuration.

Integrating with the Polymarket Relayer Client

H2: The Polymarket Relayer Client (TypeScript & Python)

Polymarket provides official Relayer Client SDKs in TypeScript and Python to simplify integration. The client handles common end-user tasks so your integration can focus on routing logic and order strategy.

What the client manages for you:

• Wallet deployment and Proxy or Gnosis Safe handling
• ERC-20 approvals for pUSD
• CTF operations (split/merge/redeem) for outcome tokens
• Order creation and cancellation, including market orders exposed as FAK
• Signing requests with the builder attribution headers when requested

Using the Relayer Client reduces engineering friction and ensures requests conform to Polymarket's relayer expectations (rate limits, headers, and CLOB semantics).

Practical integration checklist

H2: Implementation checklist for builders

1. Obtain credentials
   • Get your builder credentials and set your tier at polymarket.com/settings. This controls your relayer limits and reward eligibility.
2. Pick an SDK
   • Use the TypeScript or Python Relayer Client to accelerate integration and avoid low-level misconfigurations.
3. Add attribution
   • Ensure every routed order includes the required attribution headers so the Relayer can credit your builder account.
4. Handle approvals and wallets
   • Use the client to manage pUSD approvals and wallet deployment; the Relayer sponsors gas, so end users remain gasless.
5. Monitor limits
   • Implement quotas in your system to avoid exceeding daily relayer limits for your tier. Unverified builders are limited to 100/day, Verified 10,000/day, Partner is unlimited.
6. Account for fees and settlement
   • Track builder fee accruals in basis points and reconcile with weekly rewards if you're Verified or Partner.

Accounting and revenue share considerations

H2: How payments flow

• Builder fees accrue on execution and are denominated in basis points of the trade.
• Verified builders receive weekly USDC rewards based on volume in addition to builder fees; Partner tier receives enhanced rewards per Polymarket's program.
• Polymarket manages actual payouts and the formulas behind the weekly rewards; builders should use the dashboard at polymarket.com/settings for reporting and payment details.

Operational and risk notes

• Relayer rate limits matter: enforce local throttles to avoid rejected requests and unexpected behaviour.
• Trades routed through the Relayer are subject to Polymarket's CLOB rules: tick size behaviour, FAK semantics for market orders, and maker/taker fee rules (makers pay zero maker fees).
• Builders do not remove other risks inherent to prediction-market trading: resolution risk (UMA disputes can delay settlement), slippage and partial fills, and smart-contract risk. Always surface those risks to your users.

How this affects your trading infrastructure

H2: Practical impact on your systems

If you operate a routing layer or aggregator, the Builder Program changes two things: you can receive direct revenue for orders you route, and you must manage attribution and relayer limits. Use the Relayer Client for wallet and token ops to avoid re-implementing CTF and gasless logic. Design your system to record attribution per order, track accrued basis-point fees, and reconcile weekly payouts from Polymarket.

Closing summary

The Polymarket Builder Program is a developer-focused route to add order flow to the Polymarket CLOB with attribution and a revenue share. For builders, the main operational tasks are obtaining credentials, integrating attribution headers, using the Polymarket Relayer Client (TypeScript or Python), and respecting tiered relayer limits. Builder fees are paid in basis points at execution, and Verified/Partner builders receive additional reward mechanisms managed by Polymarket.

For more technical detail on the CLOB and market semantics, see /guides/polymarket-clob-explained and to understand fee structure on Polymarket see /guides/polymarket-fees-explained.

Frequently asked questions

What are the Polymarket Builder Program tiers and limits?

There are three tiers: Unverified (100 daily relayer limit), Verified (10,000 daily relayer limit plus weekly USDC rewards and builder fees), and Partner (unlimited relayer limit and elevated support). These tiers control rate limits and reward eligibility.

How are Polymarket builder fees paid?

Builder fees are configured in basis points and paid to the credited builder when an order executes. Verified builders also receive weekly USDC rewards based on volume; exact payout mechanics are managed by Polymarket.

Do I need to manage gas or wallet deployment?

No. The Polymarket Relayer sponsors gas for end users. The Relayer Client SDK (TypeScript and Python) handles wallet deployment (Proxy or Gnosis Safe), pUSD approvals, and CTF operations so you can focus on routing logic.

How do I make sure my trades are credited to my builder account?

Include the required attribution headers on routed requests. The Relayer uses those headers to credit your builder. Use the official Relayer Client to ensure headers and signing are correct.

Where do I get builder credentials and settings?

Builder credentials and tier settings are managed at polymarket.com/settings. That dashboard controls credential issuance, tier assignment, and reporting.