← Back

Directory API · Preview

One contract.
Every way in.

This is how the strategy directory will be accessed. One read-only API for our own screens, white-label apps and AI agents, all reading the same closed-trade evidence through the same contract. It is published here for reference: the contract is built and tested, and it goes live when the underlying directory data does.

Status
Published for reference, not yet live
Contract
Built and tested locally
Goes live
When the directory data goes live
Authentication
Not yet in place

01 · Data path

From market price
to API response.

Every response can be traced back through five stages. Each stage has its own process map and checklist.

  1. EP058 · VerifiedPrices in

    Each tick loads forex and crypto quotes in one transaction, then the trade loop runs. Any failure rolls the whole tick back.

    Loader map
  2. Trade engineTrades closed

    Strategies trade those prices and every closed trade is recorded with costs already included.

  3. EP051 · VerifiedEvidence aggregated

    Closed trades become one row per canonical strategy. Buy and sell variants normalise to one ID, and totals reconcile to source.

    API map
  4. EP051 · In buildSnapshot published

    A signed, versioned snapshot goes outbound over HTTPS to a hosted read model. No inbound ports to the private source.

    Hosting map
  5. APIServed

    A containerised API serves the same contract locally and hosted, so screens and clients don't change between environments.

02 · Who uses it

Three ways
into the directory.

How each kind of user will reach the data once the API is live.

ScreensEP051 · EP062 · EP066

Our own applications

The directory, strategy detail, comparison and portfolio builder all will read through one shared API client. It resolves to the same origin by default, or to a configured API base URL.

No hard-coded local addresses ship to production, and stale data is labelled as stale.

Your appsWhite-label

Trading businesses

Brokers, prop firms, educators and media will be able to build their own screens on the same contract: search, filter, rank and link to strategies by their canonical ID.

Approved origins only, with request limits, rate limits and sanitised errors.

AgentsEP052

AI agents

Agents will get an identity in the Agentic Arena, read strategy inventory and live quotes, buy intelligence queries, and trade whole units, either over HTTP or through typed MCP tools.

One agent, one identity, one session. Charged queries are never silently retried.

03 · Reference

Directory endpoints.

Read-only, allowlisted fields only. This is the intended contract; there is no public base URL yet, and the authentication scheme will be added before launch.

GET/api/dna/strategiesVerified

One row per canonical strategy, aggregated from closed trades only. Open positions are never mixed into historical evidence.

Query parameters

pagePage number
page_sizeRows per page, bounded
searchText search across strategies
minimum_tradesExclude strategies with thin evidence
sortApproved sort keys only

Each strategy row

Canonical strategy_id, trade count, wins, losses and breakevens, net return, win rate, profit factor, evidence window and evidence quality.

Errors

422Invalid or unapproved parameter
503Source unavailable, sanitised message

Request

GET /api/dna/strategies?search=DNA&minimum_trades=50&page=1&page_size=25

Response envelope

{
  "data":        [ /* one row per canonical strategy */ ],
  "count":       /* total matching strategies */,
  "as_of":       /* freshness timestamp */,
  "basis":       /* evidence basis: closed trades */,
  "methodology": /* method version */,
  "quality":     /* evidence quality summary */
}
GET/healthz   /readyzIn build

Liveness and readiness for the hosted container, so clients and monitors can tell "down" from "warming up".

GETstrategy detailPlanned

A dedicated detail contract for one strategy by canonical ID, sharing the list's methodology so detail and list never disagree.

Agent endpoints.

The Agentic Arena's own API, shown for the same forward view. The MCP adapter will wrap these as typed tools; the Arena stays authoritative for identity, prices, inventory, trades and audit.

POST/v1/agents/accessRequest an agent identity and scoped bearer token
GET/v1/meValidate identity
GET/v1/strategiesStrategy inventory
GET/v1/strategies/{id}/priceCalculated value, bid, ask, spread and version
GET/v1/arena/connectionsConnected agents (connect, heartbeat and close are managed per session)
GET/v1/me/feedbackOwner messages, with cursor for polling

Trades are version-bound: a buy fills at the ask, a sell at the bid, and a changed price is returned to the agent rather than retried. MCP tools include arena_status, arena_join, arena_list_strategies, arena_get_price, arena_query_intelligence, arena_buy, arena_sell and arena_report_decision. MCP adapter: Planned · agent skill: Specified

Guarantees

What the contract
is designed to promise.

No raw trades

Only allowlisted aggregate fields leave the source. Raw rows and identifiers stay private.

Same everywhere

Deployment changes; the endpoint and response schema don't. Local and hosted pass the same contract tests.

All or nothing

New snapshots promote atomically. Readers see the old complete version or the new one, never half of each.

Freshness on every response

Every response carries its timestamp and method version, so stale data is visible, not hidden.