malformedlisted in Coinbase#3 by calls of 16 on this host
0.9 USDC
per call, as the listing declares it on eip155:
- Validation state
- malformed
- Uptime, 7 / 30 / 90 days
- 0% / 44% / 44%
- 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.9 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.
At the sweep of 2026-10-21 it answered 402 but failed the required checks bazaar.schema and parse.
For reputation score the failing check asks whether a Bazaar JSON schema is present.
api.limitguard.ai serves reputation score, a POST endpoint that TOLL places in identity, listed in the Coinbase registry.
Per call, reputation score declares 0.9 USDC on Base.
Its declared inputs are a json body with the field entity_name.
For reputation score the listing declares 3 accepts on Base and Solana, to 2 different wallets.
reputation score returns json; the example shows trend, confidence, reputation_score and verification_count.
reputation score drew a single call from a single payer in the trailing 30 days.
The last call to reputation score came 2 days before the snapshot, 2026-10-11.
Among the 16 endpoints on api.limitguard.ai, reputation score is tied 3rd by calls with 13 others.
Of the calls counted across api.limitguard.ai, reputation score takes 6%.
reputation score is near the top of prices in identity; 98% of comparable listings are cheaper.
Closest in price to reputation score within identity: sanctions check at api.strale.io and reviews at www.cultos.dev.
reputation score declares exact and settled-transfer as payment schemes.
The payee wallet is shared by 16 listings on one host.
The listing for reputation score fails only advisory checks about output metadata; the verdict is unaffected.
TOLL's first observation of reputation score was 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.9 USDC | exact | 0x6454a6…7B8843 |
| Coinbase | solana: | USDC | 0.9 USDC | exact | P9Mqh3W5…T7FbEQ |
| Coinbase | eip155: | USDC | 0.9 USDC | settled-transfer | 0x6454a6…7B8843 |
the checks, as of 2026-10-21 20:54 UTC · method · pinnableendpoint answered HTTP 402
bazaar.info.output· advisory, does not affect the verdict · output metadata is present (advisory)bazaar.schema· a Bazaar JSON schema is presentparse· the discovery extension parsed
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-21 20:54 UTC | malformed | 3 | daily-2026-10-21 |
| 2026-10-19 11:05 UTC | malformed | 3 | daily-2026-10-19 |
| 2026-10-18 19:34 UTC | malformed | 3 | daily-2026-10-18 |
| 2026-10-16 08:54 UTC | malformed | 3 | daily-2026-10-16 |
| 2026-10-15 10:51 UTC | malformed | 3 | daily-2026-10-15 |
| 2026-10-14 08:41 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 13:34 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 10:58 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-12 05:28 UTC | pass | 0 | 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": {
"body": {
"entity_name": "Acme B.V."
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"trend": "stable",
"confidence": 0.87,
"reputation_score": 92,
"verification_count": 12
}
}
}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 score on api.limitguard.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-limitguard-ai-v1-reputation-score-be75a4/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-limitguard-ai-v1-reputation-score-be75a4-2026-10-13T14-08Z,
author = {TOLL},
title = {reputation score on api.limitguard.ai},
howpublished = {\url{https://tollindex.com/e/api-limitguard-ai-v1-reputation-score-be75a4/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.