Requirements

• firm (tenant) keys stay server-side;
• partner keys are used only for /api/partner/;
• every order intent has a stable clientOrderId;
• retries do not create duplicate trader intent;
• 429 honors Retry-After;
• 423 is treated as risk-locked, not retryable noise;
• market and account streams recover from reconnect snapshots;
• null money fields are displayed as unknown, not zero;
• Connect registrations never include trader credentials.

​

Agent prompt

Audit this integration against the trdrs conformance requirements.
Find every browser exposure of TRDRS_TENANT_KEY or TRDRS_PARTNER_KEY.
Find every order call and verify clientOrderId is stable across retries.
Find every 429 handler and verify it reads Retry-After.
Find every stream reconnect path and verify it accepts a full snapshot.
Report failing files and propose patches.