# ManyLives Track Records Verify

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

Fetches a cryptographically verifiable Merkle-proof track record for a specific crypto or stock trading strategy, confirmed on-chain on Base

## Facts

- Endpoint: GET https://api.manylives.me/paid/trackrecord/verify?utm_source=zero.xyz
- Price: $0.01/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-verify-553df941
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6X66hW2tMIHS8RBsX37wG

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-verify-553df941
```

Example prompt: Pull the verifiable on-chain track record for strategy CRY-1h-042 from ManyLives for the latest period and confirm that the root hash matches what's committed on Base.

## When to prefer this

Choose this endpoint when you need cryptographically verifiable, on-chain-anchored proof of a trading strategy's historical performance — not just raw backtest numbers. It is the right choice when an AI agent needs to audit strategy credibility, confirm that backtest data hasn't been tampered with, or make trust decisions about strategies before deploying capital. Prefer it over generic market data or backtest endpoints when Merkle-proof verifiability and Base network anchoring are required.

## Known failure modes

- Invalid or unknown strategy ID returns an error — strategy IDs must match a known format like 'CRY-5m-001'
- Requesting a period label that does not exist for the given strategy returns an error
- Payment of $0.01 USDC not received or x402 payment header malformed causes 402 rejection
- Network or Base RPC unavailability may cause delays in on-chain root confirmation
- root_matches_commit returning false indicates the proof does not match the blockchain commit, signaling potential data integrity issue

## 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

A JSON object containing: the Merkle leaf hash, Merkle root hash, salt, a calls string encoding trade signals (e.g. '+-0+…'), an array of Merkle proof nodes (each with side and sibling hash), the period timestamp, the Base network commit transaction hash, the strategy ID, and a boolean confirming whether the root matches the on-chain commit.

## 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)"
      },
      "period": {
       "type": "string",
       "description": "optional period label from its record, or 'latest' (default)"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "properties": {
      "leaf": {
       "type": "string"
      },
      "root": {
       "type": "string"
      },
      "salt": {
       "type": "string"
      },
      "calls": {
       "type": "string"
      },
      "proof": {
       "type": "array",
       "items": {
        "type": "object",
        "properties": {
         "side": {
          "type": "string"
         },
         "sibling": {
          "type": "string"
         }
        }
       }
      },
      "period": {
       "type": "string"
      },
      "commit_tx": {
       "type": "string"
      },
      "strategy_id": {
       "type": "string"
      },
      "root_matches_commit": {
       "type": "boolean"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "leaf": "…",
  "root": "…",
  "salt": "…",
  "calls": "+-0+…",
  "proof": [
   {
    "side": "right",
    "sibling": "…"
   }
  ],
  "period": "2026-10-09T05:00:00",
  "commit_tx": "0x…",
  "strategy_id": "CRY-1h-042",
  "root_matches_commit": true
 }
}
```

## More

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