Step zero — from nothing to your first trade

1. Create the account. Open myriad.markets, connect the EOA you will trade from, and follow the current prompts; the repo sources do not document the identity-check sequence.
2. Set up credentials. Create a wallet and secure its seed phrase; never share the private key, which Predictefy never sees. Get an API key and secret in your venue account’s API settings, bound to that EOA. For hosted submit or cancel, the HMAC pair transits one bounded request and is never retained.
3. Fund and approve. A practical first test is $10–$25—not a venue minimum—of the market-selected 18-decimal USD1 or USDT on BNB Smart Chain (56), plus a little BNB for approval gas. Myriad has no venue-pinned bridge helper. For cross-chain funds, use GET /v1/bridge/quote only as an explicit chain/token quote; set chain 56 and the exact market collateral, then verify both before signing.
4. Allow time. Budget 1–2 hours for a first wallet and funding; less if the asset is ready.

The repo sources document no Myriad geographic gate.

What you need first

• Production status: Armed for Order Book build, submit, and cancel as verified on 2026-08-15.
• Wallet and chain: An EOA on BNB Smart Chain (56) signs the EIP-712 order client-side.
• Venue account: Yes. Use a current Myriad API key and secret bound to the same connected EOA; bare, non-wallet-bound credentials are unsupported.
• Credentials: Keep the HMAC key and secret in your process and send them only with hosted submit or cancel. Predictefy reads them after signature recovery and never retains them.
• Funding: The manager-selected, 18-decimal BSC collateral: code-pinned USD1 or USDT. Fund the EOA and approve the exchange’s required collateral or outcome shares; there is no hosted helper.

Myriad is a strict server-built Order Book lane. It is source-ready but default off behind exact literal MYRIAD_TRADE_ENABLED=true; check GET /v1/exec/venues before integrating. Send a canonical model-qualified outcome id as asset (or outcome) plus these fields:

Production update — 2026-08-15

The default-off wording above records the source-ready phase. Production now advertises build, submit, and cancel for Myriad’s Order Book lane; AMM ids remain unsupported by this order path.

Field	Type	Required	Meaning
isBuy	boolean	yes	true → native side 0; false → native side 1
price	decimal 0.01..1.00	yes	Limit price on Myriad’s mandatory 0.01 tick grid
size	positive decimal	yes	Share amount, scaled by live collateral decimals
owner	EVM address	yes	EOA trader that signs and owns the venue API key

Only myriad:ob:56:{marketId}:0|1 reaches order construction. The catalog lookup uses the exact qualified outcome and must provide matching native market/outcome provenance. Every build then reads the exact Order Book market, proves BSC chain 56 plus deployed exchange/manager/token code, obtains the market collateral from getMarketCollateral, reads decimals, and requires agreement with the API. Supported collateral is code-pinned to 18-decimal BSC USD1 or USDT. Any missing or conflicting identity, model, generation, code, collateral, or decimal fact fails closed.

The returned buildVersion: 1 artifact includes the complete EIP-712 domain, canonical ordered types, message, market and collateral provenance, and structHash. The signed nonce is generated from 256 bits of server CSPRNG entropy. Orders are SDK-compatible GTC limits with expiration and minimum fill set to zero. Sign the typed data in your wallet, then submit { executionId, signature, owner, apiKey, apiSecret }. Predictefy recovers the EOA over the stored digest before reading either credential, then HMAC-SHA256 signs the exact POST /orders bytes.

Cancel builds a zero-notional artifact from the original stored order and wallet signature. Submit the cancel execution with { executionId, owner, apiKey, apiSecret }; the service HMAC-signs one DELETE /orders/:orderHash request. The key, secret, and generated headers are never persisted or logged. The configured venue endpoint must be a clean HTTPS origin and redirects are rejected. Use a current Myriad key/secret bound to the same connected wallet; bare-key auth is not supported. There is no hosted status refresh, modify, account, or funding-helper lane.

Canonical myriad:amm:... outcomes return typed NOT_SUPPORTED. AMM trading uses Myriad’s separate quote/calldata wallet-transaction lifecycle and is never sent through Order Book signing logic. The existing resolved-AMM claim lane is an independent deployment capability.