# ManyLives Track Records

> ManyLives Track Records is a paid API for AI agents from manylives.me, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-10).

Fetches a trading strategy's verified track record dossier including returns, luck analysis, proof integrity, and peer ranking by strategy ID.

## Facts

- Endpoint: GET https://manylives.me/paid/trackrecord/dossier?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-track-records-cec346eb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e-dYr1wH2uegUVc0uAZgI

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 manylives-track-records-cec346eb
```

Example prompt: Pull the full track record dossier for strategy CRY-5m-001 — I want to see its return percentage, whether its gains look like skill or luck, its 30-day rank in the book, and whether the proof integrity check passes.

## When to prefer this

Use this endpoint when you need a structured, verifiable, single-strategy performance dossier that includes both quantitative track record data (returns, ranking) and qualitative/statistical signals (luck verdict, proof integrity). Prefer this over generic market data endpoints when you specifically need strategy-level attribution, Merkle proof verification, or peer ranking context for a known strategy ID.

## Known failure modes

- Missing or invalid strategy ID returns an error or empty response
- Unknown strategy ID not in the book returns a 404 or null dossier
- Stale proof data if the strategy has not submitted a recent proof
- Network or payment failure (x402 payment not accepted) blocks access
- Strategy ID format mismatch (wrong prefix or format) causes lookup failure

## How this service works

No forms, no dropdowns. Describe the outcome in plain words and the Brain asks what it must, lists the job, collects offers and recommends one.

## Output

A JSON dossier containing the strategy's ID, a luck verdict (e.g. 'consistent with luck' or 'statistically significant'), a record object with return percentage, a latest_proof object indicating whether the Merkle root matches the committed root, the strategy's 30-day rank within the strategy book, and its correlation coefficient to the top 20 strategies.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "examples": [
        "CRY-5m-001"
       ],
       "description": "strategy id (required)"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string"
      },
      "luck": {
       "type": "object",
       "properties": {
        "verdict": {
         "type": "string"
        }
       }
      },
      "record": {
       "type": "object",
       "properties": {
        "return_pct": {
         "type": "number"
        }
       }
      },
      "latest_proof": {
       "type": "object",
       "properties": {
        "root_matches_commit": {
         "type": "boolean"
        }
       }
      },
      "rank_in_book_30d": {
       "type": "number"
      },
      "correlation_to_top20": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "CRY-1h-042",
  "luck": {
   "verdict": "consistent with luck"
  },
  "record": {
   "return_pct": 4.1
  },
  "latest_proof": {
   "root_matches_commit": true
  },
  "rank_in_book_30d": 12,
  "correlation_to_top20": 0.18
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-track-records-cec346eb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from manylives.me](https://www.zero.xyz/host/manylives.me/llms.txt)