Bring your agent to Optix.
Give your agent market context, test a thesis, and follow the decision through to your record. You choose its permissions. You control execution.
On this page
Connect your agent
Optix exposes a remote Model Context Protocol (MCP) server. Use a client that supports Streamable HTTP and browser-based OAuth with public-client registration and PKCE.
- Sign in and open Agents in the Optix app.
- Copy the MCP address shown there. The app supplies the address for its configured environment; it ends in
/mcp. - Add that address to your agent as an HTTP MCP server.
- Complete the browser sign-in and approve the requested permissions in Optix.
For Claude Code, replace YOUR_OPTIX_MCP_URL with the copied address:
claude mcp add --transport http optix YOUR_OPTIX_MCP_URL
For clients that accept an MCP server configuration:
{
"mcpServers": {
"optix": {
"type": "http",
"url": "YOUR_OPTIX_MCP_URL"
}
}
}
Your client manages OAuth. There is no static API key to paste into this configuration. Keep tokens and brokerage credentials out of prompts.
Choose permissions
The connection belongs to the signed-in Optix account. Start with the access your workflow needs and review connected agents in Agents.
| Scope | What it enables |
|---|---|
optix:read | 15 tools for analysis, thesis drafts, review, account context, and this connection’s order history. |
optix:read optix:trade | All 20 tools, including order preparation, approved submission, cancellation requests, and broker reconciliation. |
optix:read does allow log_thesis to save a draft. Saving a Just predict forecast requires optix:trade; with read access, a forecast request is saved as a draft instead. Neither action places an order.
Trading scope makes execution tools available; an order still needs approval of its exact terms or a submission policy you configured. An agent cannot enable or expand its own authorization. Adding trading scope requires a new consent flow.
You can revoke a connection in Agents. Revocation removes its future access; it does not cancel orders already sent to a provider. The agent name on the consent screen is supplied by the client, not an Optix verification of that client.
Start with a thesis
First discover what your connection can do. Then ask for context, form a view, and inspect the trade before deciding what to save or place.
{
"name": "get_capabilities",
"arguments": {}
}
This is the params object for an MCP tools/call request. Your MCP client normally handles the protocol envelope.
Get current context for a symbol:
{
"name": "market_context",
"arguments": { "symbol": "NVDA" }
}
A useful prompt for your connected agent:
Get the latest NVDA context and available expiries. Help me test a 60% chance of finishing above $213 with a $200 maximum loss. Ask me to confirm the deadline and distribution assumptions before running the analysis.
test_thesis accepts a symbol, an explicit future deadline, a thesis distribution, and a maximum loss in dollars. The distribution uses either a central target or an above/below probability at a price, plus spreadPercent. Shape, skew, and an implied-volatility shift can refine those assumptions.
The result uses the same thesis engine as the Optix app: Best fit and ranked alternatives, with sizing and risk context. These are model outputs under the supplied assumptions. A target or probability is your view, not a guaranteed price path.
To continue without placing a trade:
Save this as a draft thesis. Show me the suggested risk and why this structure fits. Keep execution for my review in Optix.
Use list_open_theses to return to that record, review_trade after a position closes, and get_score to see the account’s rating and forecast record.
Tool reference
Optix currently defines 20 tools. The server exposes the tools permitted by your OAuth grant. Use MCP tools/list for the current argument schemas and descriptions; account and feature availability can impose additional checks.
Market & analysis
Scope: optix:read
| Tool | Purpose |
|---|---|
get_capabilities | Discover supported analysis, execution, scopes, and access. No arguments. |
market_context | Get sourced prices, session context, available option expiries, and chart history for a symbol. |
option_chain | Read listed contracts and quotes for a symbol and expiry, with optional right, strike, and pagination filters. |
test_thesis | Test a deadline target or probability distribution and return the app’s ranked trade choices and suggested sizing. |
evaluate_strategy | Evaluate supplied option legs or a position, cost basis, and scenarios against the thesis. |
size_trade | Inspect suggested risk and the constraints that set it. Does not place an order. |
Thesis & record
Scope: optix:read, with the forecast exception below.
| Tool | Purpose |
|---|---|
log_thesis | Save text or a structured thesis. draft is the default; forecast requires trading scope. practice saves a draft to place in the app. Never submits an order. |
list_open_theses | List your open theses and their status. Optional limit: 1–100, default 20. |
review_trade | Read Decision and Prediction verdicts for a closed trade, identified by a thesis, intent, or supplied legs. |
get_score | Read your rating, uncertainty range, level, and the five score components. |
replay_event | Explore a historical earnings event from the pre-announcement view. The outcome stays hidden until reveal. |
Accounts & order history
Scope: optix:read
| Tool | Purpose |
|---|---|
account_context | Read connected execution accounts, imported holdings, permissions, and freshness. Returns no credentials. |
get_order | Read a persisted order, its thesis, approval state, and fill evidence for this agent grant. Does not refresh the broker. |
list_orders | Read the bounded order history belonging to this agent grant. |
trade_record | Read this grant’s submitted orders, original theses, and actual fills. Use review_trade for a graded review. |
Agent order history is not a complete brokerage history. Imported holdings also do not imply permission to trade those accounts.
Execution
Scope: optix:trade, in addition to read access.
| Tool | Purpose |
|---|---|
prepare_order | Prepare exact contracts, thesis assumptions, risk budget, and a fresh broker review using a stable idempotency key. Returns approval and policy eligibility; does not submit. |
prepare_close_order | Prepare a close for an owned, complete Optix Paper package. Live closing is unavailable. |
submit_order | Submit an approved intent after fresh broker and policy checks. Cannot grant itself authorization. |
cancel_order | Request cancellation of this agent’s order. Provider evidence must confirm the cancellation. |
reconcile_order | Refresh the original intent against the broker without submitting a new order. Uncertain states may remain unresolved. |
Order approvals
Analysis and execution are separate steps. A recommendation, saved thesis, or connected tracking account does not authorize a trade.
- Inspect the account. Use
account_contextto verify the connection, permissions, supported actions, and exposure freshness. - Prepare exact terms. Call
prepare_orderwith the confirmed thesis, contracts, all-in risk budget, and one stable idempotency key for the intended order. Preparation does not reserve policy budget. - Get authorization. Open the returned approval URL and approve the exact terms, or use an eligible account-specific submission policy configured by you in Optix Agents.
- Submit and verify. Submit the prepared intent, then inspect the returned state and fill evidence. An accepted request is not necessarily a filled order.
If a submission times out or its state is unclear, use get_order and reconcile_order on the existing intent. Do not create another intent or a new idempotency key to retry it.
Challenge orders require a draft thesisId and always wait for your approval in Optix. Automatic submission policies do not bypass that requirement. A thesis deadline does not automatically close an order.
Cancellation is a request: fills can still occur while it is pending. Check the provider-confirmed state before treating an order as canceled.
Capabilities & limits
Call get_capabilities for server support and account_context for your actual connections. Current support includes:
- Analysis: US stock and ETF options, including long calls, long puts, debit verticals, and long butterflies. Exact-position evaluation can support broader analysis than execution.
- Execution: Robinhood Agentic and Optix Paper, subject to account access. Opening support is DAY limit orders for long options, debit verticals, and symmetric debit butterflies.
- Closing: Verified whole Optix Paper packages only. Live closing is unavailable.
- Not currently supported: Prediction-market or crypto construction, and scheduled monitoring.
| Limit | Current value |
|---|---|
| Requests | 120 per minute per user |
| Default tool limit | 20 calls per tool per minute per user |
test_thesis | 10 calls per minute per user |
log_thesis | 12 calls per minute per user |
| Review, score, open theses & replay | review_trade, get_score, list_open_theses, and replay_event each allow 30 calls per minute per user |
| Agent forecasts | 20 Just predict forecasts per agent grant, per user, per New York day. Further requests save drafts. |
| Request body | 64,000 bytes |
| Messages | One JSON-RPC message per request; no batch arrays |
Respect the returned retry delay when rate limited. Prices and account exposure may be stale or incomplete; preserve the source timestamps and those qualifications when presenting a result.
Protocol details
The configured endpoint is /mcp on the app’s MCP origin. The implementation uses stateless Streamable HTTP with JSON responses. It accepts MCP messages by POST and preflight OPTIONS; standalone SSE sessions are not offered.
OAuth discovery & authentication
These paths are relative to the origin of the address copied from Agents:
- Authorization server metadata
/.well-known/oauth-authorization-server- Protected resource metadata
/.well-known/oauth-protected-resource/mcp- Public-client registration
/mcp/register- Authorization
/mcp/authorize- Token exchange & refresh
/mcp/token- Revocation
/mcp/revoke
The flow uses authorization codes with PKCE S256, refresh tokens, and public clients with token endpoint authentication method none. Client ID Metadata Documents are not supported.
Send the access token in the Authorization: Bearer header. Access tokens in query parameters are rejected. Hosted deployments use HTTPS; local development permits a configured loopback HTTP origin.
Tool discovery & results
After the MCP client completes initialization, request the schemas available to its grant:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {}
}
Successful tool output includes ok: true, data, and an ISO returnedAt timestamp. That timestamp records when Optix returned the result, not when the underlying market quote was observed.
Tool failures return ok: false and an error object with code, message, and an optional retryAfter. The MCP result is marked as an error. Authentication and transport failures may instead be HTTP error responses.
Guide resource & thesis prompt
The optix://guide resource provides usage guidance. The explore_thesis prompt accepts a thesis string from 1 to 2,000 characters and guides the client through reference price, deadline, and explicit assumptions.
Troubleshooting
- The app does not show a connection address.
- The deployment must have a valid configured Optix app URL. Use the address shown by Agents when available; do not guess a hostname from the landing page.
- The client cannot complete sign-in.
- Check support for HTTP MCP, OAuth discovery, public-client registration, and PKCE. A cloud-hosted client cannot reach a server running on your computer’s localhost.
- Trading tools are missing.
- Reconnect requesting
optix:read optix:tradeand complete new consent. Then check account permissions withaccount_context. - The server rejects the host or origin.
- Use the exact configured URL from Agents. Browser clients must also use an origin allowed by that deployment.
- Order submission or cancellation is uncertain.
- Read the existing order and reconcile it. Preserve the uncertainty until provider evidence confirms the state; do not submit a replacement order as a retry.
Manage connections and permissions in Optix Agents.