Is a trading strategy's record skill or luck
Is a trading strategy's record skill or luck? Its hit rate against a coin flip (z-score and p-value), the same p-value adjusted for every strategy tested in its book (Holm), how it ranks against the book's coin-flip strategies, and how many more calls it woul…
by manylives.me · discovered, not yet claimed by its owner · updated 2026-10-09
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Is a trading strategy's record skill or luck? Its hit rate against a coin flip (z-score and p-value), the same p-value adjusted for every strategy tested in its book (Holm), how it ranks against the book's coin-flip strategies, and how many more calls it would need to be significant. Historical, scored periods only; general information, not advice.
Tags: bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-09
{
"id": "CRY-5m-001"
}{
"calls": 2400,
"hit_rate": 0.523,
"holm_adjusted_p": 0.9,
"id": "CRY-1h-042",
"p_value_one_sided": 0.012,
"verdict": "looks good on its own, but could be luck once you allow for how many strategies were tested",
"window": "all time"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/57188.jsonfor the price and payment options. - Pay. Call
GET https://manylives.me/paid/trackrecord/luck. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.03 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 1 calls · 1 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.03 | 0xD161874249321F8AE3000C19DdD070e46682f1B3 | 120s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0xD161874249321F8AE3000C19DdD070e46682f1B3",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "30000",
"amountUsd": 0.03,
"maxTimeoutSeconds": 120
}
]Schemas
Output schema (JSON Schema)
{
"type": "object"
}Example shape — generated from the schema, not a captured live response
{}Examples
curl "https://manylives.me/paid/trackrecord/luck"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://manylives.me/paid/trackrecord/luck");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://manylives.me/paid/trackrecord/luck")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- manylives.me
- Endpoint
- https://manylives.me/paid/trackrecord/luck
- Machine-readable
/resources/57188.json