# ManyLives Track Records – Timing Verification

> ManyLives Track Records – Timing Verification 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).

Returns on-chain timing proof for a specific crypto or stock strategy backtest period, showing when results were committed to the Base blockchain relative to the period start.

## Facts

- Endpoint: GET https://api.manylives.me/paid/trackrecord/timing?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-timing-verification-4b078de4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yY7Mf3LOhryFcs0YxKwiX

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-timing-verification-4b078de4
```

Example prompt: Can you pull the on-chain timing proof for the CRY-5m book on ManyLives and show me whether the results were committed to Base before the latest period started — and how many seconds ahead?

## When to prefer this

Use this endpoint when you need cryptographic, on-chain timing proof that a trading strategy's backtest results were committed to the Base blockchain before the relevant period began — distinguishing it from any self-reported or off-chain track record. Prefer this over general market data endpoints when the goal is auditing or verifying strategy integrity rather than retrieving price or signal data.

## Known failure modes

- Invalid or unknown book ID returns an error or empty response
- Requesting a period that does not exist for the given book returns no data
- Network or payment failure returns HTTP 402 or 5xx
- The 'seconds_before_start' being negative would indicate post-period commitment (a red flag for the strategy)

## 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 Base network transaction hash, the book ID, the period label, the period start timestamp, a boolean indicating whether the Merkle root is in the transaction calldata, the actual block timestamp when it was committed on-chain, and the number of seconds before the period start that the commitment was made.

## 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": [
      "book"
     ],
     "properties": {
      "book": {
       "type": "string",
       "examples": [
        "CRY-5m"
       ],
       "description": "book id (required), e.g. CRY-5m"
      },
      "period": {
       "type": "string",
       "description": "optional period label, or 'latest' (default)"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "properties": {
      "tx": {
       "type": "string"
      },
      "book": {
       "type": "string"
      },
      "period": {
       "type": "string"
      },
      "period_start": {
       "type": "string"
      },
      "root_in_calldata": {
       "type": "boolean"
      },
      "block_time_onchain": {
       "type": "string"
      },
      "seconds_before_start": {
       "type": "number"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tx": "0x…",
  "book": "CRY-5m",
  "period": "2026-10-09T05:05:00",
  "period_start": "2026-10-09T05:05:00Z",
  "root_in_calldata": true,
  "block_time_onchain": "2026-10-09T05:03:41Z",
  "seconds_before_start": 79
 }
}
```

## More

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