canonical: https://jentic.com/apis/tradier.com/tradier

# Tradier Brokerage API

Tradier Brokerage API provides a comprehensive REST API for US-based equities and options trading. Access market data, place trades, manage accounts, and stream real-time data for building trading applications. The API exposes 28 endpoints secured with bearer authentication.

## For AI agents

Programmatically get user profile, get account balances. Covers 28 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get User Profile
- Place Order
- Integrate Tradier Brokerage API into automated workflows
- Query and filter Tradier Brokerage API records by parameters
- Monitor Tradier Brokerage API operational status and events

## Use cases

### Developer Tools Operations

Use the Tradier Brokerage API to perform developer tools operations programmatically. The API provides 28 endpoints covering core functionality including get user profile, get account balances, get positions.

Example prompt: Call GET `/user/profile` to get user profile

### Automated User Data Management

Automate user data operations by combining multiple Tradier Brokerage API endpoints. Agents can get account balances and then get positions in a single workflow.

Example prompt: Call GET `/accounts/{account_id}/balances` to get account balances, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tradier Brokerage API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get user profile', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/user/profile` | Get User Profile |
| GET | `/accounts/{account_id}/balances` | Get Account Balances |
| GET | `/accounts/{account_id}/positions` | Get Positions |
| GET | `/accounts/{account_id}/history` | Get Account History |
| GET | `/accounts/{account_id}/gainloss` | Get Gain/Loss |
| POST | `/accounts/{account_id}/orders` | Place Order |
| GET | `/accounts/{account_id}/orders` | Get Orders |
| GET | `/accounts/{account_id}/orders/{order_id}` | Get Order |

## Key resources

- **User Data** — User profile information
- **Account Data** — Account balances, positions, and history
- **Trading** — Order placement, modification, and cancellation
- **Market Data** — Real-time quotes, historical pricing, and market information
- **Watchlists** — Watchlist management

## Why Jentic

- **Setup:** Wiring the Tradier Brokerage API by hand means managing its bearer token auth, picking the production or sandbox host, and handling errors yourself. Through Jentic you install once, import the Tradier Brokerage API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Tradier puts the account id in the URL path (`/accounts/{account_id}/...`), so a rule can pin your agent to one account: it can read that account's balances, positions, and history and nothing else. You choose the operations it may call, so placing an order is not included unless you add it.
- **Credential handling:** Your Tradier bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get account balances' or 'place an equity order', and Jentic returns the matching Tradier Brokerage API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Tradier Brokerage API use?

The Tradier Brokerage API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get user profile with the Tradier Brokerage API?

Yes. Use the GET `/user/profile` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tradier Brokerage API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get user profile through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get user profile'. Jentic returns the matching Tradier Brokerage API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tradier Brokerage API have?

The Tradier Brokerage API exposes 28 endpoints covering user data, account data, trading operations.

### Can I limit what my agent is allowed to do with the Tradier Brokerage API?

Yes. Because Jentic One is self-hosted by you, your own rules decide which Tradier operations and credentials the agent may use. Since Tradier puts the account id in the URL path (`/accounts/{account_id}/...`), you can pin the agent to a single account and allow only read calls such as balances, positions, and history. Write operations like placing an order through POST `/accounts/{account_id}/orders` are excluded unless you explicitly add them.