crypto history derived
api.manylives.meMarket dataderived
GET https://api.manylives.me/paid/crypto/history
passlisted in Coinbase#16 by calls of 142 on this host
0.003 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-09 22:06 UTC
- First observed by TOLLderived
- 2026-10-09
- Pricederived
- 0.003 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 12 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
crypto history shares api.manylives.me with 141 other listed endpoints and is tied 16th by calls with 94 others.
Callers of crypto history supply the query parameters date and coins.
The declared response carries date and prices.
crypto history drew 2 calls from 2 unique payers in the trailing 30 days, every call from a different payer.
crypto history was last called 4 days before the snapshot.
A call to crypto history costs 0.003 USDC on Base, as declared.
TOLL files crypto history under market data: a GET endpoint on api.manylives.me, listed in the Coinbase registry.
crypto history answered the sweep of 2026-10-15 with a valid 402, as at every sweep since 2026-10-09.
Closest in price to crypto history within market data: chain erc20 balance at api.onesource.io and perp funding at agent402.tools.
crypto history is priced above 13% of comparable listings in market data.
The wallet paid by crypto history is the payee of 266 endpoints across 2 hosts.
The seller's own tags are trading, crypto, market-data and prices.
The price of crypto history is declared by 648 other listings in market data too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0xD16187…82f1B3 |
the checks, as of 2026-10-15 10:43 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-15 10:43 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 08:34 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 13:27 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 10:51 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 09:32 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 17:41 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 13:46 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-09 13:30 UTC | pass | 0 | new-after-daily-2026-10-09 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-09 22:06 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"date": "2026-01-01",
"coins": "BTC"
}
},
"output": {
"type": "json",
"example": {
"date": "2026-01-01",
"prices": [
{
"usd": 90000,
"coin": "BTC",
"time": "…",
"symbol": "BTC"
}
]
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "crypto history on api.manylives.me", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-manylives-me-paid-crypto-history-ba7e68/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-manylives-me-paid-crypto-history-ba7e68-2026-10-13T14-08Z,
author = {TOLL},
title = {crypto history on api.manylives.me},
howpublished = {\url{https://tollindex.com/e/api-manylives-me-paid-crypto-history-ba7e68/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.