Bridge & Funding
The polygolem bridge family wraps Polymarket’s Bridge API. Use it to discover
supported chains and create a deposit address that the bridge will credit as
pUSD on Polygon.
Supported assets
polygolem bridge assets{ "supportedAssets": [ { "chainId": "8453", "chainName": "Base", "token": { "name": "USD Coin", "symbol": "USDC", "address": "0x...", "decimals": 6 }, "minCheckoutUsd": 45 } ]}Create a deposit address
The bridge issues a one-shot address scoped to your destination wallet. Send supported collateral to this address from the chosen source chain, and the bridge credits pUSD to the destination wallet on Polygon:
polygolem bridge deposit 0xYourPolymarketWallet{ "address": { "evm": "0x...", "svm": "...", "btc": "bc1..." }, "note": "Only certain chains and tokens are supported. See /supported-assets for details."}Quote and status SDK methods
The public Go SDK also wraps POST /quote and GET /status/{address}:
client := bridge.NewClient("", nil)quote, err := client.GetQuote(ctx, bridge.QuoteRequest{ /* ... */ })status, err := client.GetDepositStatus(ctx, depositAddress)Those endpoints do not have CLI commands yet. Use Bridge API for the exact request and response contracts.
What’s next after bridging
The deposit wallet flow is required for all trading:
POLYMARKET_PRIVATE_KEY="0x..." \ polygolem deposit-wallet onboard --fund-amount 0.71Read Deposit Wallets & Signature Types for the full explanation.
Reference
polygolem bridge --help— every flagdocs/COMMANDS.md— canonical command list- Bridge API — endpoint mapping
- Deposit Wallets & Signature Types — required for post-May-2026 accounts