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

# Prop firms

> For prop firms and anyone with no venue of their own: issue evaluation accounts on the trdrs venue, govern their risk, and run the evaluations business over your partner key.

**You have no venue of your own. Use ours.**

A prop firm's accounts come from us: evaluation accounts issued on the trdrs venue, traded on
the platform with simulated capital against live markets. You issue them, set the risk that
governs them, and follow every change from your back office — the trader just signs in and
trades.

This is one of the two ways a firm gets a trader trading. The other is registering an account that
already exists at a venue of your own, and [Two ways in](/guides/account-paths) sets them side by
side.

## What you can build

* **An evaluations business** — [issue accounts](/guides/issue-accounts) in batches of up to 20, each tied to a trader's sign-in email and your own `referenceId`, with one bad email failing only its own item.
* **Risk that enforces itself** — [five controls per account](/guides/govern-account-risk) (daily and weekly loss, daily and weekly profit, an end-of-day close 1–240 minutes before the bell), live from the moment you write them; a control that fires flattens and locks the account.
* **The full lifecycle** — halt trading, resume it, reset an evaluation to its starting state. A halt blocks new orders without closing anything; only a reset gets the account flat.
* **A ledger you can audit** — [record balance operations](/guides/record-balance-operations) for payouts, credits and corrections, each keyed on your own reference so a retried pipeline can never pay out twice.
* **Billing you can reconcile** — [read your usage](/guides/read-your-usage) and the accounts behind it, from the same query the invoice is computed from.
* **A back office that stops polling** — `account.reset`, `balance.recorded`, `risk.locked` and `risk.unlocked` [delivered to your server](/guides/receive-events) as they happen.

## Core objects

An issued account, its risk controls, and a balance operation. All under
[Firm accounts](/api-reference/firm-accounts/create-evaluation-accounts) in the reference. The
usage reads sit under [Connect](/api-reference/connect/get-monthly-usage), because the meter is one
meter however the account arrived.

## Where to go next

<Columns cols={2}>
  <Card title="Run firm accounts" icon="building" href="/guides/run-firm-accounts">
    The whole surface in one short tour, one call per step.
  </Card>

  <Card title="Issue evaluation accounts" icon="user-plus" href="/guides/issue-accounts">
    The batch shape, the per-item results, and what balance means.
  </Card>

  <Card title="Govern account risk" icon="lock" href="/guides/govern-account-risk">
    Five controls, and halt versus resume versus reset.
  </Card>

  <Card title="Record balance operations" icon="receipt" href="/guides/record-balance-operations">
    Payouts, credits, corrections, and the ledger they land on.
  </Card>

  <Card title="Read your usage" icon="chart-simple" href="/guides/read-your-usage">
    What the meter counts, and how to reconcile an invoice.
  </Card>

  <Card title="Connect Overview" icon="link" href="/guides/connect-overview">
    Registering accounts you issued at your own venue — the same surface a broker uses.
  </Card>

  <Card title="Receive events" icon="bell" href="/guides/receive-events">
    Signed deliveries, retries, and the delivery log.
  </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>
</Columns>