faillisted in Coinbase#1 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% / 19% / 19%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-11 00:25 UTC
- First observed by TOLLderived
- 2026-09-24
- 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 2 times across 59 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 HTTP 400 rather than 402, so TOLL records it as failing.
compliance readiness, a GET endpoint on api.limitguard.ai, appears in the Coinbase registry; TOLL's taxonomy puts it in inference.
Per call, compliance readiness declares 0.11 USDC on Base.
The listing describes the request as the query parameters system_type and completed_items.
compliance readiness accepts payment on Base and Solana, 3 options in all, to 2 different wallets.
A response from compliance readiness, as declared, includes gaps, note, basis, urgency, entity_id, risk_level and 2 others.
The registry's counters give compliance readiness 2 calls and 2 unique payers over 30 days, every call from a different payer.
compliance readiness was last called 3 days before the snapshot.
api.limitguard.ai lists 16 endpoints; compliance readiness is tied 1st by calls with 1 other.
Of the calls counted across api.limitguard.ai, compliance readiness takes 11%.
98% of the 8,876 comparable listings in inference ask less.
compliance readiness sits nearest in price to translate (api.strale.io) and profiles enrich (api.linkedpanda.com) among listings in inference.
compliance readiness declares exact and settled-transfer as payment schemes.
The payee wallet is shared by 16 listings on one host.
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:20 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:20 UTC | fail | 1 | daily-2026-10-21 |
| 2026-10-20 10:56 UTC | fail | 1 | daily-2026-10-20 |
| 2026-10-19 08:32 UTC | fail | 1 | daily-2026-10-19 |
| 2026-10-18 10:31 UTC | fail | 1 | daily-2026-10-18 |
| 2026-10-17 20:49 UTC | fail | 1 | daily-2026-10-17 |
| 2026-10-16 06:42 UTC | fail | 1 | daily-2026-10-16 |
| 2026-10-15 08:27 UTC | fail | 1 | daily-2026-10-15 |
| 2026-10-14 06:32 UTC | fail | 1 | daily-2026-10-14 |
| 2026-10-13 11:14 UTC | fail | 1 | daily-2026-10-13 |
| 2026-10-12 08:36 UTC | fail | 1 | daily-2026-10-12 |
| 2026-10-11 07:20 UTC | fail | 1 | daily-2026-10-11 |
| 2026-10-10 15:24 UTC | fail | 1 | daily-2026-10-10 |
| 2026-10-09 07:59 UTC | fail | 1 | daily-2026-10-09 |
| 2026-10-08 09:28 UTC | fail | 1 | daily-2026-10-08 |
| 2026-10-07 08:48 UTC | fail | 1 | daily-2026-10-07 |
| 2026-10-06 09:41 UTC | fail | 1 | daily-2026-10-06 |
| 2026-10-05 08:39 UTC | fail | 1 | daily-2026-10-05 |
| 2026-10-04 11:03 UTC | fail | 1 | daily-2026-10-04 |
| 2026-10-03 05:51 UTC | fail | 1 | daily-2026-10-03 |
| 2026-10-02 15:04 UTC | fail | 1 | daily-2026-10-02 |
| 2026-10-01 07:57 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:17 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 19:33 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 06:20 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 21:04 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-25 19:21 UTC | fail | 1 | new-after-daily-2026-09-24 |
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 00:25 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"system_type": "trust_scoring",
"completed_items": "risk_management"
}
},
"output": {
"type": "json",
"example": {
"gaps": [
{
"id": "data_governance",
"requirement": "Data governance and quality (Art. 10)"
},
{
"id": "technical_docs",
"requirement": "Technical documentation (Art. 11)"
},
{
"id": "record_keeping",
"requirement": "Automatic logging/record-keeping (Art. 12)"
},
{
"id": "transparency",
"requirement": "Transparency and information to users (Art. 13)"
},
{
"id": "human_oversight",
"requirement": "Human oversight measures (Art. 14)"
},
{
"id": "accuracy_robustness",
"requirement": "Accuracy, robustness, cybersecurity (Art. 15)"
}
],
"note": "Self-assessment: the score counts the completed_items you sent against the 7 EU AI Act high-risk obligations. entity_id is your label; nothing is looked up about it.",
"basis": "self_assessment",
"urgency": "critical",
"entity_id": "acme-ai",
"risk_level": "HIGH",
"system_type": "trust_scoring",
"total_items": 7,
"completed_items": 1,
"readiness_score": 14,
"days_until_enforcement": 0
}
}
}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, "compliance readiness on api.limitguard.ai", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/api-limitguard-ai-v1-compliance-readiness-entity-id-6de676/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-api-limitguard-ai-v1-compliance-readiness-entity-id-6de676-2026-10-13T14-08Z,
author = {TOLL},
title = {compliance readiness on api.limitguard.ai},
howpublished = {\url{https://tollindex.com/e/api-limitguard-ai-v1-compliance-readiness-entity-id-6de676/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.