# ManyLives Track Records Find

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

Search and filter 2,000+ verifiable crypto and stock trading strategy track records by performance, horizon, market, and statistical significance

## Facts

- Endpoint: GET https://api.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-find-c2445ba1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cgnCiVQZzNElS_nTAwkzt

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-find-c2445ba1
```

Example prompt: Find me the top 10 crypto strategies with a 1-hour prediction horizon that returned at least 5% after costs over the last 7 days and passed the statistical significance filter — sort by return.

## When to prefer this

Use this endpoint when you need to discover or rank pre-existing backtested trading strategies by performance metrics, statistical significance, or market segment. Prefer this over general market data endpoints when the goal is to select a strategy rather than retrieve price data. Ideal when an AI trading agent needs to pick a strategy to follow based on verifiable historical track records locked on the Base network.

## Known failure modes

- No strategies match the specified filters — returns empty matches array
- Invalid parameter values (e.g. non-numeric min_return_pct) cause a 400 error
- limit exceeds maximum of 50 — capped or rejected
- as_of date in the future or before data availability — no results or error
- Payment not processed via x402 — 402 Payment Required response
- q filter too strict combined with other filters — zero matches

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

Returns a JSON object with the matched time window, count of matching strategies, the filter conditions applied, and an array of strategy objects each containing at minimum a strategy ID and after-costs return percentage. Additional fields may include hit rate, significance scores, and period counts depending on what was requested.

## 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-find-c2445ba1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)