# ManyLives Track Records – Best Monthly Hit Rate

> ManyLives Track Records – Best Monthly Hit Rate 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).

Returns a ranked list of trading strategies with the highest correct directional call rate (hit rate) over a 1-month window, including multi-timeframe performance data.

## Facts

- Endpoint: GET https://manylives.me/paid/strategies/1mo-best-hit-rate?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-best-monthly-hit-rate-2aa41f4f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ymn84lTynPEzm7Behl4h4

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-best-monthly-hit-rate-2aa41f4f
```

Example prompt: Show me the strategies with the highest hit rate for monthly directional calls — I want to see which ones were most accurate at predicting up or down moves, ranked by correctness, at an intermediate level.

## When to prefer this

Use this endpoint when you specifically need to rank trading strategies by directional accuracy (hit rate) rather than raw returns or Sharpe ratio. It is best when the user cares about how often a strategy is *right* about market direction on monthly timeframes, not just how much it made. Prefer it over generic market data endpoints when evaluating strategy track records for selection or backtesting purposes.

## Known failure modes

- No strategies meet the filter criteria — empty results list returned
- Payment not processed (x402 protocol failure) — endpoint returns 402 before data is served
- Malformed input schema — missing required vs. properties fields cause a 400 error
- Data freshness issues — simulated data sources marked with asterisk may lag real-time conditions
- Ambiguous query parameters — overly broad or missing criteria may return unexpected rankings

## 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 a ranked list of trading strategies scored by directional hit rate on monthly calls over a 1-year period. Each entry includes a strategy ID, rank, and multi-timeframe performance windows (e.g. 1h, 5y) with return percentages and data source labels (on-chain or simulated). Also includes the level (e.g. intermediate) and the criteria used for ranking.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "list": "Most accurate monthly strategies",
  "level": "intermediate",
  "results": [
   {
    "id": "CRY-1h-042",
    "rank": 1,
    "all_windows": {
     "1h": {
      "source": "on-chain",
      "return_pct": 0.4
     },
     "5y": {
      "source": "simulated*",
      "return_pct": 120.5
     }
    }
   }
  ],
  "criteria": "monthly calls, highest share of correct up/down calls over 1y"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-track-records-best-monthly-hit-rate-2aa41f4f/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)