Skip to main content
Each use case covers who it’s for, what you build, the call sequence, a starter you can run, and the guardrails that keep it safe. Every operation links to its page in the API reference, where you can try it.

Best price execution across venues

One order, filled at the best combined price across Polymarket and Hyperliquid, without integrating either venue.

Model driven trading with hard limits

A bot that turns model edge into orders, with spending caps the API enforces.

An AI agent that trades within a budget

A research agent on a read only key proposes trades; an execution key with tight limits places them after approval.

Hedging sportsbook exposure

Buy the other side on prediction market liquidity when liability crosses a threshold.

Price monitoring and alerts

Dashboards and alerts on a read only key, with no trading permission at all.

Funding and treasury automation

Find deposit assets and addresses, then watch balances arrive.

Guardrails built into every key

Every use case runs on the same controls:
  • Spending caps on every key. A per order limit and a rolling 24 hour limit, checked before anything reaches a venue. A key can lower its own limits, never raise them.
  • Idempotent orders. Your client_order_id makes every retry return the original order, never a second one.
  • Read only keys. A key with only the read scope can see markets, quotes and previews, and can never place an order.
  • Kill switch. One call pauses a key or its whole trading account.
  • Preview first. See the exact venue plan, cost and any refusal before you commit.

Start with a test key

All starters use the same two variables as the Quickstart:
A test key lets you try everything without real money: orders and fills are simulated against test balances of 10,000 USD on each venue. Switch to a live key when you’re ready. See Test mode and live mode.