Build with AI

Give a coding agent these docs and the API contract, store a sandbox key in your server’s environment, and have it build your integration. Use this page when you’d rather describe the job and review the result than write every call yourself. The agent reads the guides and the contract, makes one authenticated request to prove the setup, then builds the job you gave it. By the end you have a working first request and a prompt for the job, and you know how to check what the agent built.

​

Keep keys out of the prompt

Put the key in your backend’s secret environment, and tell the agent the variable’s name, never its value. Don’t put a key in a prompt, commit it, or ship it in browser or mobile code. The prompts on Agent prompts use TRDRS_TRADING_API_KEY, TRDRS_VENUE_KEY, TRDRS_API_KEY for a Connect app’s API key, and TRDRS_PRE_REGISTRATION_KEY.

​

Make one working request

Before the agent builds anything, have it prove the key and the base URL with one read that changes nothing.

1. Follow Choose your quickstart to create the key your job needs. Venue keys come from the back office’s API keys page, Trading API keys from your trdrs profile, and Connect API keys from the Connect dashboard.
2. Store it on your server and set TRDRS_API_BASE_URL=https://sandbox.trdrs.co.
3. With a Trading API key, call GET /api/instruments. With a Venue key, call GET /api/venues/{venueId}/instruments/active, where a new venue’s empty list is still a success. With a Connect app’s API key, call GET /api/account/list naming a trader your app has never linked in x-trdrs-trader, where 404 trader_not_found is the success.
4. Expect 200 for the Trading API key and Venue key reads. For a new Connect trader, the expected 404 trader_not_found confirms that the key works. For a Trading API key, select Check request status in API access to confirm that its first request arrived.

Then give the agent the prompt for its job.

​

Pick the key for the job

A Venue key runs one venue from your backend, its setup and its accounts. A Connect app’s API key creates Connect links and, naming a trader on each request, reads that trader’s accounts and routes their orders. A Trading API key reaches only its owner’s accounts. Core concepts explains venues, groups, providers and the paper book, and it’s the first page an agent should read.

​

Give the agent one job

Give each job its own prompt, and tell the agent not to invent routes the contract doesn’t list.

• Issue evaluation accounts on the paper book: Run a venue, then Venue accounts.
• Pre-register traders at a built-in provider: Connect pre-registration, for accounts that already exist at a built-in provider.
• Build your own trading interface on Connect: the Connect prompt, with the Connect quickstart, the Connect SDK and Route your traders’ orders.
• Build a trading app: Build a front end and its charting guide. Keep every key on the backend.
• Write a public provider: Provider conformance.

The venue routes are served on the sandbox. Production access is arranged when a venue qualifies. A Connect app opens its production with the Connect pass a passed conformance run earns.

​

Check what the agent built

Run the conformance prompt against your integration, then a conformance run in the sandbox. It drives your own client through retries, deliberate errors and stream reconnects, and records the result. Use dedicated test accounts, because the run injects errors and places sandbox orders. A Connect app runs its own ruleset instead: Pass Connect conformance. A passing conformance run proves the behavior it measures. It doesn’t make a venue Listed or prove every business rule.

​

Next steps