API & MCP

Drive the platform from Claude, ChatGPT, your own scripts, or a webhook. One HTTP shim — same shape as the live runner.

Endpointshttps://trading.mwmai.no

Method	Path	Purpose
GET	/api/list_cells	List all cells the loader knows about
GET	/api/list_strategies	List registered strategy modules
GET	/api/get_strategy_param_spec	Read a strategy's PARAM_SPEC (requires ?name=)
POST	/api/save_cell	Create or update a cell YAML
POST	/api/jobs	Submit a backtest job, returns job id
GET	/api/jobs/:id	Job status (queued / running / completed)
GET	/api/runs	List completed backtest runs
GET	/api/runs/:id	One run's summary stats + equity curve
GET	/api/runs/:id/trades	Trade-by-trade JSON for a run
GET	/api/healthz	Liveness check
GET	/api/get_bars	OHLCV from the DuckDB store (requires ?symbol=&timeframe=&start=&end=)
GET	/api/knowledge	Search the vector brain (books, papers, skills) — ?q=&collection=
GET	/api/knowledge/source	Walk every chunk of one source file (?source_path=&collection=)
GET	/api/live/quote	Last quote + session delta for a symbol (?symbol=)
GET	/api/ironclad/status	Per-cell 9-step Ironclad status (?cell=&start=&end=)
GET	/api/ironclad/steps	Static Ironclad step catalogue (no cell required)
POST	/api/ironclad/run_stepcoming soon	On-demand single-step trigger via the job worker
GET	/api/dry_run_backtest	One-shot backtest without queueing (requires ?cell_name=&start=&end=)

Use with Claude / ChatGPT

The read endpoints above are also wrapped as MCP tools by a local MCP server (platform-api) that proxies to this same host. Point it at https://trading.mwmai.no from your own machine, add it to your MCP client config (Claude Desktop, Claude Code, or any MCP-capable client), and you can ask things like "backtest the liquidity-sweep cell on MNQ for the last year and show me the equity curve". The server runs on your side, not ours; there is nothing to sign up for.

Auth

The read endpoints are public, no key required. There is no visitor account system and no API key to manage. The write endpoints (save cell, submit job) are gated behind HTTP basic auth at the edge and are reserved for the maintainer, so the public surface is read-only by design.