> ## 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 Overview

> Register an account that already exists at a venue, and the trader who owns it finds it waiting at sign-in — with their credential still theirs.

Connect is the handoff for an account that already exists at your venue. You tell trdrs the account
exists and name the trader who should see it; the trader signs in, finds the registration waiting,
and enters their own venue credential. Your firm never sends us a password, because [the
registration has no field for one](/api-reference/connect/create-an-account-registration).

This is one of the two ways a firm gets a trader trading. The other is having trdrs create the
account, and [Two ways in](/guides/account-paths) sets them side by side.

A broker registers an account on its own venue, under its own clearing. A prop firm registers the
evaluation account it sold, at the venue it issued that account through. The registration cannot
tell the two apart: it carries an email, an account number, and the login name you issued — and it
grants no access on its own.

## What you can build

* **A pre-filled onboarding, on either side of the business** — register the trader's email and account number, and their first sign-in lands on a connect screen that already names your firm and system. The broker's client and the prop firm's evaluation buyer see the same screen.
* **A registration pipeline that survives a retry** — registering the same `(email, accountNumber)` again refreshes the 30-day expiry instead of creating a second handoff, so a crashed batch can be re-run.
* **A clean audit trail** — [list your registrations](/api-reference/connect/list-your-registrations) to see which are pending, linked, revoked, or expired, and reconcile that against your own records.
* **A revocation path for the pending ones** — a refund or a mistake is [one call](/api-reference/connect/revoke-a-pending-registration). A linked registration is not revocable, because the trader already linked the account with a credential you never held.
* **Zero credential custody** — no password field, by design. Your firm delivers the venue credential to the trader through your own onboarding; trdrs sends no customer handoff email.
* **Billing you can check yourself** — [monthly usage](/api-reference/connect/get-monthly-usage) and [the accounts behind it](/api-reference/connect/list-billed-accounts) come from the same query the invoice does.

## Core objects

An account registration (the `registration` object on the wire) and its four statuses — pending,
linked, revoked, expired. All under
[Connect](/api-reference/connect/create-an-account-registration) in the reference.

## Where to go next

<Columns cols={2}>
  <Card title="Register an account" icon="user-plus" href="/guides/register-an-account">
    The full lifecycle: create, watch the status, expire or revoke.
  </Card>

  <Card title="Follow registrations" icon="bell" href="/guides/handle-registration-events">
    `registration.linked` and `registration.revoked`, and reconciling against the list.
  </Card>

  <Card title="Connect" icon="link" href="/partner-platform/operator-concepts/connect">
    The registration handoff, end to end.
  </Card>

  <Card title="Two ways in" icon="signs-post" href="/guides/account-paths">
    This path beside the other one, and when a firm uses each.
  </Card>

  <Card title="Brokers" icon="building-columns" href="/guides/brokers-overview">
    What a broker can do today, and what is still on the roadmap.
  </Card>

  <Card title="Bring data via your venue" icon="tower-broadcast" href="/guides/venue-data">
    Why a registered account already has market data.
  </Card>
</Columns>