Skip to main content
The public API is owned by api-router. It is endpoint-driven, family-first, and versioned under /v1.

Endpoint-driven

Public behavior is exposed through explicit HTTP routes, not internal module imports.

Family-first

The implemented public family is strategy-arena.

Thin client safe

Clients parse envelopes and call routes; they do not reimplement scoring or simulation internals.

​
Implemented public surface

MethodPathPurpose
GET/healthzpublic health check
GET/openapi/v1.jsonpublic OpenAPI document
MethodPathPurpose
GET/v1/familieslist supported and planned families
GET/v1/families/strategy-arenaStrategy Arena metadata
GET/v1/families/strategy-arena/strategieslist strategies
GET/v1/families/strategy-arena/strategies/{strategyId}read one strategy
GET/v1/families/strategy-arena/strategies/{strategyId}/parametersread parameter schema
GET/v1/families/strategy-arena/marketslist markets
MethodPathPurpose
POST/v1/families/strategy-arena/simulationsrun full simulation
POST/v1/families/strategy-arena/simulations/summaryrun compact simulation view
POST/v1/families/strategy-arena/simulations/tradesrun trade-focused simulation view
POST/v1/families/strategy-arena/evaluationsevaluate one simulation result

​
Not implemented in public v1

The current public API does not expose:
  • server-owned leaderboard endpoints,
  • public wallet or encryption flows,
  • public AMM endpoints,
  • public swap endpoints,
  • operator runtime endpoints.

​
Response envelope

Successful /v1/** responses use: 
{
  "requestId": "req_123",
  "status": "ok",
  "data": {}
}
Errors use application/problem+json with AlphaEngine extensions. See Errors.

​
Thin client ownership

A thin client should:
  • set x-api-key,
  • parse success envelopes,
  • parse problem details,
  • expose ergonomic methods such as listMarkets, runSimulation, and runEvaluation,
  • assemble beta leaderboard rows locally from evaluation results.
It should not reimplement strategy math, simulation logic, evaluation logic, contest ranking, or operator runtime behavior.

Authentication

API key behavior, error cases, and beta limit semantics.

Simulations

Full, summary, and trade-focused simulation endpoints.

Evaluations

How one simulation result becomes score and diagnostics.

How the arena works

Product flow behind the public API surface.