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

# Bring data through your venue

> Your traders' market data flows under their own venue entitlements — publishing data to them is part of issuing their accounts.

There is no feed to upload. When your trader links the venue login you issued, the engine builds
their market-data connection from that login — bars, replay, and quotes stream under the
trader's own subscription and entitlement. The engine redistributes nothing, which is why no
data-vendor agreement sits between your firm and a working chart.

## What your firm actually does

1. Issue the venue login with the market-data entitlements your traders should have — the same
   decision you already make with your venue.
2. [Register the account](/guides/register-an-account) through Connect so the trader finds it
   pre-filled at sign-in.

That is the whole integration. The trader links the account with their own credential, and
their charts stream.

## How the engine handles the feed

* One market-data connection per trader, built from their own vaulted login. A trader with
  several firms streams from one entitlement; if that login disconnects, the next request
  rebuilds from whichever remains.
* Bars and historical replay ride one long-lived connection. Live quotes ride a second,
  isolated one — a missing quote entitlement never breaks bars, so a chart works even when a
  login carries data but not level-1 quotes.
* Venues allow one live session per login: if the trader opens the same login in another
  application, the venue displaces the engine's session. The engine rebuilds once; a repeated
  displacement parks the feed rather than fighting the other application for it.

## What this does not cover

Data from a venue the engine does not connect to. For that, run a small HTTP feed and register it
with us — see [Publish a datafeed](/guides/publish-a-datafeed). It is the second choice on purpose:
a published feed is a server your firm has to keep up, while the path above is a decision you
already make with your venue.