TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-13 14:08 UTC
Sweep
daily-2026-10-21 · finished 2026-10-21 22:33 UTC
Listed
32,435

compliance readiness derived

api.limitguard.aiInferencederived

GET https://api.limitguard.ai/v1/compliance/readiness/:entity_id

faillisted in Coinbase#1 by calls of 16 on this host

0.11 USDC

per call, as the listing declares it on eip155:8453

Compare with anotherEvery figure as JSONCite this page

the price, as of 2026-10-13 14:08 UTC · method · pinnable

Validation state
fail
as of 2026-10-21 11:20 UTC · method · pinnable · sweep daily-2026-10-21
Uptime, 7 / 30 / 90 days
0% / 19% / 19%
as of 2026-10-21 11:20 UTC · method · pinnable · 0 of 7 in 7d, 5 of 26 in 30d, 5 of 26 in 90d
Calls, trailing 30 days
2
as of 2026-10-13 14:08 UTC · method · pinnable
Unique payers, trailing 30 days
2
as of 2026-10-13 14:08 UTC · method · pinnable
Last called
2026-10-11 00:25 UTC
as of 2026-10-13 14:08 UTC · method · pinnable
First observed by TOLLderived
2026-09-24
as of 2026-09-24 21:29 UTC · method · pinnable · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.11 USDC
as of 2026-10-13 14:08 UTC · method · pinnable · on eip155:8453
Networks
2
as of 2026-10-13 14:08 UTC · method · pinnable

Counters

59 observations, 2 of them a change, fewer than the 3 a trace needs

How big is this endpoint among the ones like it?

1 call100,000this endpoint
Calls counted in the trailing thirty days across the 8,525 endpoints in Inference that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 2: 1,355 in the category are counted higher and 7,169 lower.

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.

In words

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.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method · pinnable

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.11 USDCexact0x6454a6…7B8843
Coinbasesolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdpUSDC0.11 USDCexactP9Mqh3W5…T7FbEQ
Coinbaseeip155:8453USDC0.11 USDCsettled-transfer0x6454a6…7B8843

Preflight checks at the last sweep

the checks, as of 2026-10-21 11:20 UTC · method · pinnableendpoint answered HTTP 400

  • returns_402 · an unauthenticated request gets HTTP 402

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-21 11:20 UTCfail1daily-2026-10-21
2026-10-20 10:56 UTCfail1daily-2026-10-20
2026-10-19 08:32 UTCfail1daily-2026-10-19
2026-10-18 10:31 UTCfail1daily-2026-10-18
2026-10-17 20:49 UTCfail1daily-2026-10-17
2026-10-16 06:42 UTCfail1daily-2026-10-16
2026-10-15 08:27 UTCfail1daily-2026-10-15
2026-10-14 06:32 UTCfail1daily-2026-10-14
2026-10-13 11:14 UTCfail1daily-2026-10-13
2026-10-12 08:36 UTCfail1daily-2026-10-12
2026-10-11 07:20 UTCfail1daily-2026-10-11
2026-10-10 15:24 UTCfail1daily-2026-10-10
2026-10-09 07:59 UTCfail1daily-2026-10-09
2026-10-08 09:28 UTCfail1daily-2026-10-08
2026-10-07 08:48 UTCfail1daily-2026-10-07
2026-10-06 09:41 UTCfail1daily-2026-10-06
2026-10-05 08:39 UTCfail1daily-2026-10-05
2026-10-04 11:03 UTCfail1daily-2026-10-04
2026-10-03 05:51 UTCfail1daily-2026-10-03
2026-10-02 15:04 UTCfail1daily-2026-10-02
2026-10-01 07:57 UTCpass0daily-2026-10-01
2026-09-30 07:17 UTCpass0daily-2026-09-30
2026-09-29 19:33 UTCpass0daily-2026-09-29
2026-09-28 06:20 UTCpass0daily-2026-09-28
2026-09-25 21:04 UTCpass0daily-2026-09-25
2026-09-25 19:21 UTCfail1new-after-daily-2026-09-24

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

  1. listed in Coinbase

Declared input and output, as listed

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].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about compliance readiness, or reply as the named seller

No account, no token. Published unedited with its outcome, upheld or not. Do not include personal data.

Kind

Published as typed. Optional.

10 to 4,000 characters.

Verify with the payee wallet (optional, EVM)

Sign this message with the wallet named on the page and paste the signature; it is checked, stored, never published. TOLL reply about endpoint 6de6764fa34c87d34bfba7199e5159054c44fd4f911e3f4281d3ab5f3c203642 from wallet 0x6454a645C92B8722EC9A07FCe12A582A877B8843

The 0x address named as payee on this page, 42 characters.

The hex signature of the message above, starting 0x.