# Orchard Data Track Record

> Orchard Data Track Record is a paid API for AI agents from orchard-data.letom1176.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-16).

Returns a trading system's historical performance metrics including win rates by strategy lane, forecaster accuracy, and comparison against SPY benchmark.

## Facts

- Endpoint: GET https://orchard-data.letom1176.workers.dev/api/track-record
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orchard-data-track-record-e7e4a939
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_R9rco-JlOwyu9N0EoWmKw

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability orchard-data-track-record-e7e4a939
```

Example prompt: Pull up the track record for Orchard Data's trading system — I want to see the win rates by lane, the forecaster's hit rate, and how it's stacking up against SPY.

## When to prefer this

Choose this endpoint when you need a quantitative track record of a paid AI-native market data service that uses micropayments (x402/USDC), and you want to evaluate its forecasting accuracy, per-lane win rates, and benchmark comparison against SPY before committing to ongoing usage. It is specifically useful for agents that need to programmatically audit the credibility of a trading signal service.

## Known failure modes

- Payment required (402) if x402 USDC payment header is missing or insufficient
- Invalid properties filter returns empty or error response
- Service unavailable if Cloudflare Worker is down
- Rate limiting if too many calls without valid payment

## How this service works

Market data for AI agents, paid per-call via x402 (USDC on Base). Free index at /, free spec here.

## Output

A JSON object containing: an array of strategy lanes with trade counts and win rates (e.g. credit_spread), a forecaster object with live ledger hit rate and number of scored predictions plus walk-forward volatility accuracy, and a system_vs_spy comparison showing edge percentage, SPY return multiple, and system return multiple.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "lanes": [
   {
    "lane": "credit_spread",
    "trades": 2,
    "win_rate": 1
   }
  ],
  "forecaster": {
   "live_ledger": {
    "hit_rate": 0.67,
    "n_scored": 12
   },
   "walk_forward_vol_acc": 0.71
  },
  "system_vs_spy": {
   "edge_pct": 5.5,
   "spy_multiple": 1.01,
   "you_multiple": 1.07
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orchard-data-track-record-e7e4a939/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from orchard-data.letom1176.workers.dev](https://www.zero.xyz/host/orchard-data.letom1176.workers.dev/llms.txt)