machine access

Data for agents

Every page on this site is rendered from the JSON below — same bytes, no authentication, stable schemas. If you are an AI agent (or building one), this is your front door: start at /llms.txt for the agent-readable site guide. One request: the numbers describe simulated paper trading, and each document says so in its disclaimer field — carry that context with any figure you surface.

the catalog

Machine-readable endpoints

Endpoint	Contents
/data/meta.json	This document.
/data/fleet.json	All sleeves: summary stats, equity series, recent trades.
/data/momentum.json	Momentum sleeve: full equity, drawdown, trade log, stats.
/data/meanrev.json	Mean-reversion negative control: full record.
/data/vrp.json	Volatility-premium options sleeve: full record + open structure.
/data/gate.json	The pre-registered go-live gate: criteria, progress, binding interpretation.
/data/killlist.json	Every strategy idea tested and rejected, with reasons.
/llms.txt	Agent-readable site guide.
/api/mcp	Live read-only MCP server (streamable HTTP): fleet_overview, sleeve_record, gate_status, kill_list, site_guide.

Try it

# latest equity + stats for every sleeve
curl -s https://thales.report/data/fleet.json | jq '.sleeves[] | {sleeve, equity: .stats.equity, clean_return: .stats.clean_return}'

# the full momentum trade log
curl -s https://thales.report/data/momentum.json | jq '.trades[:5]'

# what has been tried and killed
curl -s https://thales.report/data/killlist.json | jq '.entries[] | {name, verdict}'

Schema stability

Fields are added, never renamed or removed, within a major version of the site. Dates are ISO YYYY-MM-DD; money is USD; returns are decimal fractions (0.01 = 1%). Each document carries generated_at.

MCP server — live

A read-only Model Context Protocol (MCP) server runs at /api/mcp (streamable HTTP) with five tools: fleet_overview, sleeve_record, gate_status, kill_list, site_guide. Information only — no trading or advice tools exist, by design.

# Claude Code
claude mcp add --transport http thales \
  https://thales.report/api/mcp

Verification

What you can and cannot independently check today.

State files are maintained in a git repository and committed by automation after each trading run, giving the record CI-stamped, tamper-evident history. A public verification mirror is planned; until then, treat performance as claimed-but-not-yet-independently-verifiable — exactly the standard we apply to everyone else.