Venues

The capability matrix — venues, frameworks, regions, requirements.

GET/context/venues#

The agent's first read after getting a key: everything deployable, in one response.

Response — 200

{
  "venues": [
    {
      "id": "hyperliquid",
      "name": "Hyperliquid",
      "frameworks": ["freqtrade", "nautilus"],
      "credentials": [
        { "type": "managed", "required": false },
        { "type": "byok", "status": "coming_soon", "scoped_key_supported": true }
      ],
      "min_deposit_usd": 5,
      "regions": ["us-central1"]
    }
  ]
}

Live Nautilus backtest support#

The live matrix includes these venues for Nautilus backtesting. They are not available for Nautilus paper deployments.

Coming soon#

BYOK is also coming soon. The live credential path is the managed wallet.

Reading the matrix#

• frameworks — which runtimes can execute against this venue. Pick your framework and venue together; POST /runtime/deployments validates the combination against this same matrix and rejects unsupported pairs with unsupported_framework_venue.
• credentials — the live credential path is managed. BYOK fields and scoped-key validation are coming soon.
• regions — where the runtime physically runs. Latency to the venue's matching engine is the reason regions exist; the default is always the venue's best region.
• min_deposit_usd — below this, the venue itself rejects orders or account setup; the runtime surfaces that as a deployment error rather than silently idling.

This registry is small, static, and versioned with the API — safe to cache for hours, cheap to re-read.