examples/maker-bot/ provisions both directions and runs a fixed-price strategy with a separate quote key. It is an integration example, not a profitable strategy.

​
Inspect the deployment

Check chain IDs, contracts, tokens, decimals, settlement timings and the operator against independently reviewed configuration; /v1/info is not a signing trust root. /health returns 503 until watchers and relay capacity are ready.

​
Provision with the financial key

Link the owner’s accounts on both venues in the app; the example expects the financial key to own both. From examples/maker-bot:
The amounts fund Hyperliquid, then Polymarket; a nonzero side needs at least 5 tokens. maker.json holds the credential bearer and client order IDs with private permissions: keep it, and rerun with it after an interruption so no second order is funded. Delegated orders start without a quote; the quote key activates them. If a margin transfer ends unknown, reconcile it before any new transfer.

​
Quote with the delegated key

On the strategy host, which never needs the financial key:
Each price is receive-token units per supply-token unit for its direction. Every ten seconds the bot renews a 30-second lease and replaces both quotes in one batch, with a 25-second admission window. On stop it cancels its identity’s quotes; if that fails, lease expiry stops admissions.

​
The HTTP quote lifecycle

For a custom client, persist the identity and order IDs, then:
  1. Renew the lease:
  2. Prepare a draft with POST /v1/orders/{order_id}/quotes/prepare, computing valid_until from a synchronized clock:
  3. Check the returned QuoteSet (signer, sequence, amounts, recipient, domain, expiry) against your own configuration and sign it with the quote key.
  4. Submit only {"draft_id":"…","signature":"0x…"} to PUT /v1/orders/{order_id}/quotes, or several drafts at once to POST /v1/quotes/batch.
Track inventory with /v1/me/exposure and a private snapshot plus replay (Streaming and recovery). Renew the lease only while the strategy is healthy.