Skip to guide
NoahAI
NOAH’S GUIDE · LEARN BY DOING

Connect venue and AI APIs

Distinguish account connectivity from optional AI assistance, then issue keys and verify them in the client.

Reviewed 5 Oct 2026 · Confirm availability in your installed client.

Two distinct keys

Venue keys connect market/account data and permitted orders. Optional AI provider keys enable explanations and source analysis. Configure them in Venue API settings and AI Engine/API respectively.

Connect a venue

  1. Use the institution’s official API management or Open API application.
  2. Grant required read access first, and only required order permissions for live use. Do not grant withdrawal access.
  3. Register your public IP when required.
  4. Enter Key, Secret and Passphrase as required in the PC client. Save and test.
  5. Check broker approval, real/paper account and OS requirements; start in PAPER.

Connect one AI provider

  1. Create an API account and verify billing, quotas and available models.
  2. Issue a key and set provider budgets or usage alerts.
  3. In Settings → AI Engine/API, save the provider key and run the connection check.
  4. Assign verified models to task roles, save the settings, and test a short non-sensitive request.

Why choose a fast decision model?

A small verified model can classify short requests and choose a next step without paying for extensive reasoning each time. Complex strategy reviews may use a different model. Configure roles in AI Engine/API; a separate JEV installation is not required. This is not evidence of equal accuracy or latency, and classification cannot authorize trading.

Diagnose the error

401: credentials. 403: permissions/IP/account access. 429: local budget or provider quota/rate limit. Model errors: confirm actual account access, not just a catalog entry.