# ManyLives Track Records Finder

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

Search and rank trading strategy track records by performance, market, horizon, and statistical filters using plain-language queries or explicit parameters.

## Facts

- Endpoint: GET https://manylives.me/paid/trackrecord/find?utm_source=zero.xyz
- Price: $0.02/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-finder-d15ea24b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6m9QEw3R0I1KjYGGHbUy1

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-finder-d15ea24b
```

Example prompt: Can you pull up the top 10 crypto strategies from the last 7 days with at least a 55% hit rate and a minimum 5% after-cost return, sorted by return, and only show ones that pass the luck correction filter?

## When to prefer this

Use this endpoint when you need to discover or rank existing backtested trading strategies by their real track record performance rather than generating new signals. It is ideal when you want to filter by statistical significance (luck correction), specific markets (stocks vs crypto), prediction horizons (5m to 1mo), or time windows, and want a leaderboard-style ranked result rather than raw market data.

## Known failure modes

- No strategies match the given filters — returns empty matches array
- Invalid parameter values (e.g. malformed date, out-of-range max_q) may return errors or ignored filters
- max limit of 50 results exceeded — capped silently at 50
- Requesting a future as_of date returns no results or error
- Conflicting filters (e.g. very high min_hit_rate combined with very high min_return_pct) may return zero matches

## 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 object containing the time window, number of matched strategies, the applied filter conditions, and a ranked list of strategy objects each including their ID and after-cost return percentage. Additional fields may include hit rate and significance metrics depending on query parameters.

## 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": [
      "window"
     ],
     "properties": {
      "q": {
       "type": "string",
       "examples": [
        "hourly crypto strategies up more than 1% this week after costs"
       ],
       "description": "optional plain-language conditions; any filter below overrides what it implies"
      },
      "book": {
       "type": "string",
       "description": "optional one book id, e.g. CRY-5m or CRY-1d"
      },
      "sort": {
       "type": "string",
       "description": "optional return (default), return_gross, hit_rate, significance or periods"
      },
      "as_of": {
       "type": "string",
       "description": "optional YYYY-MM-DD: the leaderboard exactly as it stood at the end of that day (point in time; later results ignored)"
      },
      "limit": {
       "type": "string",
       "description": "optional, default 10, max 50"
      },
      "max_q": {
       "type": "string",
       "description": "optional luck limit 0-1 (0.05 = passes the many-strategies correction)"
      },
      "market": {
       "type": "string",
       "description": "optional crypto (stock books are recording, not yet served)"
      },
      "window": {
       "type": "string",
       "examples": [
        "7d"
       ],
       "description": "required lookback, e.g. 1d, 3d, 1w, 30d, 3m, 1y, all or a start date YYYY-MM-DD"
      },
      "horizon": {
       "type": "string",
       "description": "optional 5m, 1h, 1d, 1w or 1mo (how far ahead each call predicts)"
      },
      "segment": {
       "type": "string",
       "description": "optional crypto"
      },
      "cost_bps": {
       "type": "string",
       "description": "optional trading cost per side in basis points for the after-costs return (default 5)"
      },
      "min_calls": {
       "type": "string",
       "description": "optional minimum calls"
      },
      "min_periods": {
       "type": "string",
       "examples": [
        "1"
       ],
       "description": "optional minimum scored periods (default 5)"
      },
      "min_hit_rate": {
       "type": "string",
       "descri
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "window": "last 7d",
  "matches": 2,
  "conditions": {
   "market": "crypto",
   "horizon": "1h",
   "min_return_pct": 5
  },
  "strategies": [
   {
    "id": "CRY-1h-042",
    "return_pct_after_costs": 6.1
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-track-records-finder-d15ea24b/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)