> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trdrs.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect

> trdrs Connect is how a broker or prop firm puts its traders onto trdrs when the accounts already exist at a venue.

trdrs Connect is how a broker or prop firm puts its traders onto trdrs when the accounts already
exist at a venue.

The problem it solves is old and ugly: the firm wants to hand a trader a ready-to-go platform,
but the trader's venue credential should never pass through the firm. Most industry solutions
pick one: either the firm collects passwords, or the trader does all the setup alone.

Connect splits the job so each side does only its part:

1. **The firm onboards the trader directly**, including every customer message and the secure
   delivery of their venue credentials.
2. **The firm registers the account** with a partner key: the trader's email, the account number,
   and the venue login label. That is all a registration is.
3. **The trader signs in**, sees the registration waiting, and enters their own venue credential
   themselves.
4. **The account is live.** The firm gets audit and usage reporting; the trader keeps sole
   possession of their credential.

The firm never sends a password to trdrs and receives no trading access from the registration itself.
trdrs sends no customer handoff email. The credential moves from the firm to the trader through
the firm's own onboarding process, then from the trader to the engine's encrypted vault when they
submit the connect form.

## Reporting

Three reads cover the firm's side of the relationship, all under the firm's own partner key.

`GET /api/partner/connect/accounts` is the audit view: every registration the firm has made, and
whether each one is still pending, was linked, was revoked, or expired.

`GET /api/partner/usage` is the billing view: how many distinct accounts actually traded in a
month, the agreed per-account price, and the total. An account that was provisioned but never
traded is not counted, and simulated fills are never counted.

`GET /api/partner/usage/accounts` is the reconciliation view: the accounts behind that usage
number, each with the real fills that made it count and when the first and last of them happened.
The list always sums to the billed count because it is the same query expanded, so when a firm's
records disagree with an invoice, this is where the difference shows up — account by account.

Those numbers come from the same query trdrs computes its own invoice from, so a firm can check a
bill against the API instead of asking for a breakdown. Usage defaults to the previous complete
month, which is the one being invoiced; naming the current month gives month-to-date.

Use Connect when:

* the account already exists at a venue;
* the firm wants the trader trading on trdrs;
* the firm needs audit and usage reporting;
* the trader keeps control of their own credential.

The live routes are in API Reference under Connect, each with a worked example and a
ready-to-paste curl call, so a firm can pull its own registration list or its usage from its own server
with its partner key. Connect is one of the two ways a trader gets an account; the other is issuing
one on the trdrs venue, and [Two ways in](/guides/account-paths) sets them side by side.