Your agent is the CLI
Paste one sentence: “Read https://docs.optalgo.com/optalgo-llm.md and connect to my OptAlgo account.” The guide teaches your agent the whole platform in one file, written for agents, with every endpoint, limit and error code.
terminal agents
Trade from your terminal agent.
Claude Code, Codex or any coding agent reads one guide, logs in with a device code and runs the full loop: write, validate, backtest, deploy, watch, and ask you to go live.
Official Binance broker · Non-custodial · Live only when you confirm
sample data
Device login, the key never in the chat
Your agent starts a device login and you approve it in the app. The key goes straight into a file readable only by you and is never printed. For servers, a one-time claim code does the same.
The full loop from the terminal
Backtests and research runs, baskets, deploys to OptAlgo's hosted runner, live decisions and logs, and Compare with backtest that matches real trades against the backtest trade by trade.
Live, with guardrails
On Plus and Pro a key can carry the trade scope. Choose confirm-live or full autonomy, then cap it: max allocation, max leverage, allowed exchanges and a daily loss limit, all enforced by the server. Every call is logged.
faq
Questions traders ask first.
Is there an OptAlgo CLI?
Your coding agent is the CLI. Claude Code, Codex and similar agents read the OptAlgo agent guide and call the REST API for you, and Claude Code can also use the MCP connector. Developers can call the same API from any language.
Can Codex or Claude Code trade for me?
They can build, test and deploy strategies on paper. Live trading needs a Plus or Pro plan and a key with the trade scope. With confirm-live autonomy, every move to live waits for your approval in the app.
Where is my API key stored?
In a credentials file on your machine readable only by you. The guide forbids agents from printing it or pasting it into a chat, and you can revoke it any time under AI agents.
What are the API rate limits?
120 requests a minute per key, 30 a minute for signals, up to 5 keys per account. Write requests accept idempotency keys so a retry never acts twice.