# ManyLives Track Records Verifier

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

Retrieves a cryptographic Merkle-proof track record for a given trading strategy, verifiable on-chain.

## Facts

- Endpoint: GET https://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-verifier-2ff9fe8e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UBx1VC_U4E-YrO8Tf21E_

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-verifier-2ff9fe8e
```

Example prompt: Can you pull the latest verified track record for strategy CRY-5m-001 and confirm whether the root matches the on-chain commit?

## When to prefer this

Use this endpoint when you need to cryptographically verify that a trading strategy's historical call record is authentic and has been committed to the blockchain via a Merkle proof. It is the right choice when auditing strategy performance before investment, checking for tampered records, or building automated integrity monitors for quantitative trading strategies. Prefer this over manual inspection or off-chain records when tamper-evidence and on-chain verifiability are required.

## Known failure modes

- Missing or invalid 'id' query parameter returns an error or empty response
- Unknown strategy ID returns a 404 or empty result
- Invalid period label returns an error or falls back to latest
- On-chain commit transaction not yet indexed may cause root_matches_commit to be false or unavailable
- Service unavailable or payment failure returns a 402 or 5xx error

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

Returns a JSON object containing the Merkle leaf hash, Merkle root hash, a salt, a string encoding the sequence of trade calls (e.g. '+-0+…'), an array of Merkle proof siblings with their positions, the period timestamp, the on-chain commit transaction hash, the strategy ID, and a boolean indicating whether the computed root matches the on-chain commitment.

## 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-verifier-2ff9fe8e/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)