Sync strategy code
Push new Python or Node.js versions from your repository or CI pipeline, then build and backtest them.
Antei API keys let scripts, CI jobs and AI agents work with your account without a browser. Each key carries only the scopes you choose, such as reading strategies, running backtests or deploying live, and works with Antei's API key MCP endpoint and hosting API to sync code, backtest, deploy, change risk limits and read logs. A key is shown once and can be revoked at any time.
01 · How it works
Sign up at antei.ai and open API keys under Connect in your dashboard.
Give the key a label and grant only what the script or agent needs. Live deployment, agent and account scopes are marked high risk.
Copy the key when it appears. Antei keeps only a hash, so it is never shown again.
Send it as a bearer token to the API key MCP endpoint or the hosting API to sync code, run backtests and deploy.
Revoke a key from your dashboard and every request that uses it stops working at once.
02 · Capabilities
Push new Python or Node.js versions from your repository or CI pipeline, then build and backtest them.
Run backtests, check live readiness and deploy a version to paper trading or live.
Read logs, change risk limits, and pause, resume or kill deployments.
Grant read, backtest, paper or live access per key, so a CI job never holds more than it needs.
Point an MCP client at the API key endpoint for agents that run unattended, with no one there to sign in.
Keep up to 20 active keys, one for each script, server or agent, and revoke each on its own.
03 · Safety
04 · FAQ
Automate your account from scripts, CI jobs and AI agents. With the right scopes a key can sync strategy code, run backtests, deploy to paper trading or live, change risk limits, read logs, and pause, resume or kill deployments.
No. Claude Code, Codex and claude.ai connect through Antei's MCP server and sign in with a code emailed to you. API keys are for scripts, CI jobs and agents that run without a person there to sign in.
Revoke it under API keys in your dashboard and it stops working immediately. Because each key carries only its own scopes, a read or backtest key cannot deploy live, and no key can withdraw funds.
The fewest it needs. Keys created in the dashboard start with reading strategies, running backtests and reading paper results. Add live deployment, agent or account scopes only for automation you trust, since those are marked high risk.
Start with API keys