How a crypto strategy did in different market conditions
How a crypto strategy did in different market conditions: its daily results split into up vs down days and calm vs volatile days for Bitcoin (public price data), over a past window. Historical only; general information, not advice.
Answeringour last check, 2026-10-10
1 of 1checks answered this week
32 msmedian answer time
$0.03listed price per call
$0.03price it asked us
Paid test badge: not yet. The checks above are free: we call the tool without paying and read the payment request it sends back. The Verified badge needs paid calls whose answers match the promised output, and nobody can buy a badge.
Endpoint
GET https://manylives.me/paid/trackrecord/regimes
| Category | Market data |
|---|---|
| Provider host | manylives.me |
| Networks | eip155:8453 |
| Payment schemes | exact |
| Self-reported calls, 30 days | 1 from 1 payers (the provider's figure, not ours) |
Our checks, last 30 days
| Day | Result | HTTP | Asked | Time |
|---|---|---|---|---|
| 2026-10-10 | valid payment request | 402 | $0.03 | 32 ms |
Example input (from the provider)
{
"method": "GET",
"queryParams": {
"id": "CRY-5m-031",
"window": "30d"
},
"type": "http"
}
Promised output schema (from the provider)
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"input": {
"properties": {
"method": {
"const": "GET",
"type": "string"
},
"queryParams": {
"properties": {
"id": {
"description": "strategy id (required), e.g. CRY-1d-012",
"examples": [
"CRY-5m-031"
],
"type": "string"
},
"window": {
"description": "optional 30d, 3m, 1y or all (default 3m)",
"examples": [
"30d"
],
"type": "string"
}
},
"required": [
"id"
],
"type": "object"
},
"type": {
"const": "http",
"type": "string"
}
},
"required": [
"type",
"method"
],
"type": "object"
},
"output": {
"type": "object"
}
},
"required": [
"input"
],
"type": "object"
}