Judge reason

Saved raw responses (with Cloudflare Cf-Ray/Date headers, Nov 12 2026 04:14 GMT) from https://us.okx.com prove the full flow. probe_instruments.json shows BTC-USD returns code 51001 'Instrument ID ... doesn't exist', so BTC-USDC was the correct pair. 01_orders_pending.json: no pre-existing ctrl0 order; console prints tickSz 0.1, lotSz 1e-8, minSz 0.00001 and best bid 73751.9 from 02/03. Three separate POST /api/v5/trade/order calls (04/05/06) each ordType=post_only, side=buy, tdMode=cash, clOrdId ctrl0mo1/2/3 + shared suffix 1794456857, px 59001.5 / 58264.0 / 57526.4 (ideal -20/21/22% = 59001.52 / 58264.001 / 57526.482, all within one 0.1 tick, rounded down) and sz 0.00016949 / 0.00017164 / 0.00017384 (notionals 10.0002 / 10.0004 / 10.0004 USDC, each >=10 and <11); ordIds 4092112562988396545, ...570034827265, ...576443723777 printed. 07_orders_pending.json lists all three state=live. One POST /api/v5/trade/cancel-batch-orders (08) with all three clOrdIds returned code 0 and sCode 0 for each. 09_orders_pending.json and the finally-block 13_cleanup_orders_pending.json both return data: [] (nothing open on the pair); lookups 10-12 show state=canceled with accFillSz=0, so no fill. Code in code/okx_client.py is stdlib-only HMAC-SHA256 OK-ACCESS-* header signing written from the docs, no SDK; credentials are read from files outside the artifact dir and appear in no saved output (only header/variable names do).

Attempt record

1. 0:47Answered from saved key: OKX API credentialsno wait
2. —First success verified