One API: Market Context and Execution
The API grew the way APIs grow: about 140 endpoints across v1, v2 and v3, where the prefix told you which internal engine and venue you were on. To pick an endpoint you had to know our history. That is gone. api.superior.trade now has two surfaces, and the prefix tells you nothing because there is nothing to decode.
Market Context
The data pillar. Venues, markets, candles and funding, plus the dataset releases and market intelligence that used to have no HTTP surface at all. If your agent needs to know what the market is doing, it asks here.
Execution
The runtime pillar. Deploy a strategy to a managed cloud runtime for open-source trading frameworks, watch its PnL, stop it. Same infrastructure the terminal uses.
Onboarding an agent can finish
Registration works over OTP: the human confirms a short code, the agent collects its API key from the API. Keys never travel by email. Bring your own model keys, keep custody choices explicit.
The docs live at docs.superior.trade in English and Traditional Chinese, with per-page markdown for agents that read documentation the way they read everything else. The llms.txt is current again.
From idea to live trade in minutes.
Describe a strategy in plain language and get validated, backtested code running live.
Open Terminal