---
title: Introduction
description: What Superior Trade is, and how the API is organized.
---

Superior Trade is trading infrastructure for AI agents. You bring a strategy; we supply the two things an autonomous trader can't get from a laptop: **market context** and a **place to execute**. You can use the default managed trading wallet today; bring-your-own scoped keys are coming soon.

The API has exactly three parts:

| Area           | Base path  | What it does                                              |
| -------------- | ---------- | --------------------------------------------------------- |
| Account        | `/account` | Register, get an API key, manage keys and usage           |
| Market Context | `/context` | Venues, markets, candles, funding, datasets, intelligence |
| Runtime        | `/runtime` | Deploy and backtest strategies on supported frameworks    |

## Why a runtime, not a broker

Open-source frameworks like [freqtrade](https://www.freqtrade.io) and [NautilusTrader](https://nautilustrader.io) already solve strategy authoring well. What they don't solve is where the bot _runs_: home hardware sleeps, residential IPs get rate-limited or geo-blocked, and a strategy that dies mid-position is worse than no strategy at all.

Superior runs your framework for you. You send the same strategy file you'd run locally; we run it in an isolated, sandboxed runtime with venue connectivity, pinned framework versions, health monitoring, and logs you can read over the API. Your strategy code is yours — we execute it, we don't ingest it.

## Why market context

An agent deciding _what_ to trade needs history and state: which markets exist, how they've moved, what funding costs, what the crowd is doing. The `/context` pillar serves that from validated, immutable datasets — the same data our own backtesting engine consumes. If a backtest ran on it, you can read it.

## Custody is your choice

The live credential path is the default **managed trading wallet** ([details](/runtime/credentials)): Superior creates and custodies it (Privy infrastructure, the same custody behind the [Terminal](https://terminal.superior.trade)), you deposit and deploy with zero key handling, and [withdrawals](/wallet/overview) go only to your verified login wallet. **BYOK** for your own scoped key is coming soon.

## Machine-readable surface

When the API ships, the generated OpenAPI spec lives at `https://api.superior.trade/openapi.json` (produced from the same schemas that validate requests — it cannot drift). These docs are also agent-readable: every page at `/<path>.md`, indexed at [`/llms.txt`](/llms.txt). MCP-capable clients can discover the Superior MCP server at `https://docs.superior.trade/.well-known/mcp.json`; the manifest points to the authenticated Streamable HTTP server at `https://api.superior.trade/mcp`.

## Design status

> **Design preview.** These docs are the source of truth for the next version of api.superior.trade — they describe the target surface, ahead of implementation. Anything here can change until the design is confirmed; the current production API (v1/v2/v3) keeps working unchanged. See the [migration map](/reference/migration) and the [design log](/reference/design-log).
