> ## 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.
# Brokers
> Give the traders who already hold accounts with you trdrs as their front end, with their accounts still at your provider.
Give your clients trdrs as their trading front end while their accounts stay where they are. A
broker's accounts already exist at a market, under your clearing, and trdrs doesn't hold or clear
them. What your traders get is the front end: charts, an order ticket, exits, risk controls and an
account view over the account you already issued them.
This page is for brokerages and firms whose traders hold accounts at a provider. It explains the
two ways to bring them to trdrs and what each can do today.
## How your traders get in
The trader signs in to trdrs and finds your tile in Connect, the account picker in the trading app.
How they sign in to the account behind it depends on the provider's login style. With the trader's
own login, an API key or a wallet key, the trader enters it once and trdrs keeps it in its
encrypted vault. Anything the login needs from your listing, for example a system name, is already
filled in. Your firm never handles the trader's password. [Providers](/providers) lists each
provider's login style.
## Choose how to bring your traders
**List a built-in provider, and stop there.** Use this when your traders' accounts are at a
built-in provider, one of those [Providers](/providers) lists. For example, Meridian lists
"Rithmic, system Meridian": its traders pick Meridian's tile, sign in with their own login, and
trade their Meridian accounts. Meridian keeps its own back office,
[pre-registers each trader](/guides/register-an-account) so the account is waiting at sign-in, and
has nothing else to build.
**Run a broker group on a provider you connect.** Use this when you want your venue's own rules and
pricing between your traders and the market. You create a group whose route names a provider
connection and the account there. You can create and price the group today, but it can't route
orders until the connection has passed validation and an account at it is bound.
[Run a venue](/guides/run-a-venue) covers groups and routes.
Most brokers start with the first and never need the second.
## What exists today
| | Standing |
| - | - |
| Your venue's name, logo and Listing in Connect | Available. [Get listed](/guides/get-listed) |
| Pre-registering a trader's account | Available with a Partner key. [Register an account](/guides/register-an-account) |
| Market data licensed to each user, from the trader's own login | Available. [Provider data](/guides/venue-data) |
| Instruments, condition profiles and per-account limits | Available, and applied to orders on the paper book. [Run a venue](/guides/run-a-venue) |
| Routing a broker group through a provider | Refused until the connection has passed validation and an account at it is bound. |
| Your venue's limits, markup and commission on an account held at a provider | Not built yet. |
| Plugging in your own provider with your firm's credentials | The provider contract and self-check exist, but no public provider has run through a venue yet. [Provider self-check](/providers/provider-self-check) |
Everything reaches the [API reference](/api-reference/connect/pre-register-a-trader’s-account) and
the [changelog](/api/changelog) on the day it becomes callable, never before.
Selling evaluations rather than clearing accounts? Your accounts come from your venue on the
paper book instead of from a provider. Read [Prop firms](/guides/prop-firms-overview).
## Next steps
Put your name and logo on a tile in Connect.
Tell trdrs an account exists so the trader finds it waiting at sign-in.
Hear when a trader links a registered account.
Show your traders data from a market trdrs doesn't connect to.