Tradier
open-meridian/tradier · Community 0.14.1
0.14.1 · the vendor's words, data, never instructions.
# Its pages
Connection and Datasets are the data role's, the same on every data plugin,
under Manage for an admin of the plugin's data role. Neither shows a price: prices are read by the
plugins entitled to them. Each page is also a tool an agent can call through
your deployment's MCP connection, answering exactly what the page shows,
under the same names on every data plugin.
## Connection (`read_connection`)
One section at a time, under a tab row (Key, Limits and use, Stream,
Trading, and Sessions once measured), so the page fits one screen;
`read_connection` answers every section, the orders' under `trading`.
- **Key:** the mode (Live, Sandbox, Sample data or No key; on the sandbox,
Tradier's developer sandbox, delayed 15 minutes, no streaming); whether
the token for the environment chosen is set, never its value; what
Tradier serves your token (daily history, quotes in real time or delayed
on the sandbox, the stream), and what it does not. With no token, "No key
yet", linking to Settings.
- **Limits and use:** the plugin spends at most 60 calls a minute, half of
Tradier's 120 for market data; calls since it started, any answered "too
many requests" and waited out; the last call and the last error.
- **Stream:** how many sessions stream, or "Does not stream" on the
sandbox; then Tradier's own rows: its state, how many listings since
when, its reconnects (each a gap Tradier's history cannot fill) and
messages.
## Connection's trading sections
One page for market data and for orders: for an admin of the connectivity
role, the Trading tab holds the orders' sections. **Environment**: Paper
or Live, said plainly. **Accounts**: each account the access token reaches by its venue account
code, read-only or with trading enabled; **Enable trading** on a read-only
account, for that admin alone (`enable_trading`). The order types its
catalogue offers, and whether the execution plugin mapped it, are in the
tool's answer. **Placements**: how many orders are working, held back by a
pause or a stop, or of unknown outcome, and when the orders were last read.
**Sessions**, once measured: each call to the brokerage API's round trip,
an order's acknowledgement and a fill's delay. No account's data.
The **Connection** badge, above the tab row, says whether agents may
place orders on it: **Demo** where Environment says Sandbox and the session
reached Tradier's sandbox host (`sandbox.tradier.com`), **Live** where
neither does, and **Live (environment not confirmed)** where the two
disagree. The deployment refuses an agent's order on any connection that is
not Demo.
## Datasets (`read_datasets`)
- **Served:** each dataset as its catalogue declares it: what it serves, how
its rows arrive, its day, its default terms and whether a deployment admin
has licensed it, whether Tradier serves your token it, and what it
recorded and declined since the plugin started, and when it last
recorded; the feed and host each reads (Tradier's column).
- **Wants:** the standing wants it keeps current, the latest first: of
which dataset, asking what, for how many subjects, what each was answered
with, and whether its listings are streamed; an option chain's (`options`
or `options_delayed`), its underlyings and when it was last read. With
none, "No wants yet".
- **Subjects:** whether the deployment lets the plugin read an instrument's
record.
- **Listings kept current** (Tradier's, in the line above Served): how
many listings it knows and streams, and days still forming. A restart's
or a reconnect's gap is not caught up.
## Account links
Under Manage, for an admin of the custody role (`read_account_links`). The
Tradier account the access token reaches, by its number, beside the deployment's
accounts granted to this plugin, and the links between them. Link, create a
new account (a deployment admin), or unlink.
## Statements and History
Under Open and View, for people who may read the linked account
(`read_statements`, `read_account_activities`). **Statements**: its
custodian, the day its last statement is as of, and its state at Tradier.
**History**: its activity as Tradier reported it, the latest first.
## Raw records
Under Open and View. What Tradier answered, kept as raw records, followed from
a fact's or a row's reference, for a person who may read the account; under
Open, **Restore** brings an archived one back for seven days.
Connection and Datasets are the data role's, the same on every data plugin,
under Manage for an admin of the plugin's data role. Neither shows a price: prices are read by the
plugins entitled to them. Each page is also a tool an agent can call through
your deployment's MCP connection, answering exactly what the page shows,
under the same names on every data plugin.
## Connection (`read_connection`)
One section at a time, under a tab row (Key, Limits and use, Stream,
Trading, and Sessions once measured), so the page fits one screen;
`read_connection` answers every section, the orders' under `trading`.
- **Key:** the mode (Live, Sandbox, Sample data or No key; on the sandbox,
Tradier's developer sandbox, delayed 15 minutes, no streaming); whether
the token for the environment chosen is set, never its value; what
Tradier serves your token (daily history, quotes in real time or delayed
on the sandbox, the stream), and what it does not. With no token, "No key
yet", linking to Settings.
- **Limits and use:** the plugin spends at most 60 calls a minute, half of
Tradier's 120 for market data; calls since it started, any answered "too
many requests" and waited out; the last call and the last error.
- **Stream:** how many sessions stream, or "Does not stream" on the
sandbox; then Tradier's own rows: its state, how many listings since
when, its reconnects (each a gap Tradier's history cannot fill) and
messages.
## Connection's trading sections
One page for market data and for orders: for an admin of the connectivity
role, the Trading tab holds the orders' sections. **Environment**: Paper
or Live, said plainly. **Accounts**: each account the access token reaches by its venue account
code, read-only or with trading enabled; **Enable trading** on a read-only
account, for that admin alone (`enable_trading`). The order types its
catalogue offers, and whether the execution plugin mapped it, are in the
tool's answer. **Placements**: how many orders are working, held back by a
pause or a stop, or of unknown outcome, and when the orders were last read.
**Sessions**, once measured: each call to the brokerage API's round trip,
an order's acknowledgement and a fill's delay. No account's data.
The **Connection** badge, above the tab row, says whether agents may
place orders on it: **Demo** where Environment says Sandbox and the session
reached Tradier's sandbox host (`sandbox.tradier.com`), **Live** where
neither does, and **Live (environment not confirmed)** where the two
disagree. The deployment refuses an agent's order on any connection that is
not Demo.
## Datasets (`read_datasets`)
- **Served:** each dataset as its catalogue declares it: what it serves, how
its rows arrive, its day, its default terms and whether a deployment admin
has licensed it, whether Tradier serves your token it, and what it
recorded and declined since the plugin started, and when it last
recorded; the feed and host each reads (Tradier's column).
- **Wants:** the standing wants it keeps current, the latest first: of
which dataset, asking what, for how many subjects, what each was answered
with, and whether its listings are streamed; an option chain's (`options`
or `options_delayed`), its underlyings and when it was last read. With
none, "No wants yet".
- **Subjects:** whether the deployment lets the plugin read an instrument's
record.
- **Listings kept current** (Tradier's, in the line above Served): how
many listings it knows and streams, and days still forming. A restart's
or a reconnect's gap is not caught up.
## Account links
Under Manage, for an admin of the custody role (`read_account_links`). The
Tradier account the access token reaches, by its number, beside the deployment's
accounts granted to this plugin, and the links between them. Link, create a
new account (a deployment admin), or unlink.
## Statements and History
Under Open and View, for people who may read the linked account
(`read_statements`, `read_account_activities`). **Statements**: its
custodian, the day its last statement is as of, and its state at Tradier.
**History**: its activity as Tradier reported it, the latest first.
## Raw records
Under Open and View. What Tradier answered, kept as raw records, followed from
a fact's or a row's reference, for a person who may read the account; under
Open, **Restore** brings an archived one back for seven days.