faillisted in Coinbase#3 by calls of 16 on this host
0.11 USDC
per call, as the listing declares it on eip155:
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- 0% / 0% / 0%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-11 16:40 UTC
- First observed by TOLLderived
- 2026-10-11
- Pricederived
- 0.11 USDC
- Networks
- 2
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 5 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.
The sweep of 2026-10-21 found reputation history answering HTTP 400 instead of a payment challenge.
reputation history, a GET endpoint on api.limitguard.ai, appears in the Coinbase registry; TOLL's taxonomy puts it in identity.
On Base, reputation history asks 0.11 USDC per call.
The listing declares an input block with no named parameters.
reputation history accepts payment on Base and Solana, 3 options in all, to 2 different wallets.
A response from reputation history, as declared, includes history.
reputation history drew a single call from a single payer in the trailing 30 days.
The last call to reputation history came 2 days before the snapshot, 2026-10-11.
Of api.limitguard.ai's 16 listings, reputation history ranks tied 3rd by calls with 13 others.
6% of the host's counted calls go to it.
reputation history is near the top of prices in identity; 92% of comparable listings are cheaper.
Closest in price to reputation history within identity: launch sniper at api.losbeto.xyz and reviews at www.cultos.dev.
Schemes span exact and settled-transfer.
The wallet paid by reputation history is the payee of 16 endpoints on one host.
TOLL first observed it on 2026-10-11.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.11 USDC | exact | 0x6454a6…7B8843 |
| Coinbase | solana: | USDC | 0.11 USDC | exact | P9Mqh3W5…T7FbEQ |
| Coinbase | eip155: | USDC | 0.11 USDC | settled-transfer | 0x6454a6…7B8843 |
the checks, as of 2026-10-21 11:18 UTC · method · pinnableendpoint answered HTTP 400
returns_402· an unauthenticated request gets HTTP 402
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-21 11:18 UTC | fail | 1 | daily-2026-10-21 |
| 2026-10-20 10:54 UTC | fail | 1 | daily-2026-10-20 |
| 2026-10-19 08:30 UTC | fail | 1 | daily-2026-10-19 |
| 2026-10-18 10:29 UTC | fail | 1 | daily-2026-10-18 |
| 2026-10-17 20:46 UTC | fail | 1 | daily-2026-10-17 |
| 2026-10-16 06:40 UTC | fail | 1 | daily-2026-10-16 |
| 2026-10-15 08:25 UTC | fail | 1 | daily-2026-10-15 |
| 2026-10-14 06:30 UTC | fail | 1 | daily-2026-10-14 |
| 2026-10-13 11:12 UTC | fail | 1 | daily-2026-10-13 |
| 2026-10-12 08:35 UTC | fail | 1 | daily-2026-10-12 |
| 2026-10-12 05:27 UTC | fail | 1 | new-after-daily-2026-10-11 |
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-11 16:40 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET"
},
"output": {
"type": "json",
"example": {
"history": [
{
"date": "2026-01-15",
"score": 85
},
{
"date": "2026-02-15",
"score": 92
}
]
}
}
}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, "reputation history on api.limitguard.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-limitguard-ai-v1-reputation-history-entity-hash-6ccb1f/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-limitguard-ai-v1-reputation-history-entity-hash-6ccb1f-2026-10-13T14-08Z,
author = {TOLL},
title = {reputation history on api.limitguard.ai},
howpublished = {\url{https://tollindex.com/e/api-limitguard-ai-v1-reputation-history-entity-hash-6ccb1f/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.