TOLL

What software pays for, recorded every six hours.

Snapshot
2026-11-01 21:59 UTC
Sweep
daily-2026-10-30 · finished 2026-10-30 13:00 UTC
Listed
52,265

entities filing risk snapshot derived

api.jpverify.comOtherderived

GET https://api.jpverify.com/v1/entities/:entity_id/filing-risk-snapshot

passabsent from every registry#4 by calls of 6 on this host

0.05 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-10 05:49 UTC · method

Validation state
pass
as of 2026-10-09 08:42 UTC · method · sweep daily-2026-10-09
Uptime, 7 / 30 / 90 days
— / 100% / 96%
as of 2026-10-09 08:42 UTC · method · 0 of 0 in 7d, 7 of 7 in 30d, 24 of 25 in 90d
Calls, trailing 30 days
1
as of 2026-10-10 05:49 UTC · method
Unique payers, trailing 30 days
1
as of 2026-10-10 05:49 UTC · method
Last called
2026-09-10 06:18 UTC
as of 2026-10-10 05:49 UTC · method
First observed by TOLLderived
2026-09-10
as of 2026-09-10 19:08 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived
0.05 USDC
as of 2026-10-10 05:49 UTC · method · on eip155:8453
Networks
1
as of 2026-10-10 05:49 UTC · method

Counters

113 observations, 1 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 4,403 endpoints in Other that carry counters, binned on a logarithmic scale because the range runs over five orders of magnitude. The marked bin is this endpoint, at 1: 3,070 in the category are counted higher and 1,332 lower.

No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 113 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

TOLL files entities filing risk snapshot under the "other" category: a GET endpoint on api.jpverify.com, listed in neither registry at the last pull.

entities filing risk snapshot is priced at 0.05 USDC on Base.

The listing describes the request as the path parameter entity_id.

entities filing risk snapshot returns json; the example shows as_of, entity, source, filings, decision, limitations and 2 others.

entities filing risk snapshot answered the sweep of 2026-10-09 with a valid 402, passing 24 of 25 sweeps since 2026-09-11.

entities filing risk snapshot shares api.jpverify.com with 5 other listed endpoints and is tied 4th by calls with 3 others.

entities filing risk snapshot takes 8% of the calls counted across api.jpverify.com.

In the trailing 30 days: one call, one payer.

entities filing risk snapshot was last called 53 days before the snapshot.

Closest in price to entities filing risk snapshot within the "other" category: base64 encode url at api.strale.io and shop buy at x402.clashofcoins.com.

entities filing risk snapshot is priced above 90% of comparable listings in the "other" category.

The wallet paid by entities filing risk snapshot is the payee of 18 endpoints on one host.

The seller's tags on entities filing risk snapshot are sec, edgar, filings and disclosure.

entities filing risk snapshot was missing from the Coinbase registry at the pull of 2026-10-10, confirmed at the pull of 2026-10-10; that is registry presence, not liveness.

The price of entities filing risk snapshot is declared by 172 other listings in the "other" category too.

Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.

Payment options as declared

the payment options, as of 2026-10-10 05:49 UTC · method

Every payment option declared on this listing
registrynetworkassetamountschemepay to
Coinbaseeip155:8453USDC0.05 USDCexact0xe4A4E5…70572F

Preflight checks at the last sweep

the checks, as of 2026-10-09 08:42 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTCstatefailed checkssweep
2026-10-09 08:42 UTCpass0daily-2026-10-09
2026-10-08 10:11 UTCpass0daily-2026-10-08
2026-10-07 09:34 UTCpass0daily-2026-10-07
2026-10-06 10:19 UTCpass0daily-2026-10-06
2026-10-05 09:14 UTCpass0daily-2026-10-05
2026-10-04 11:32 UTCpass0daily-2026-10-04
2026-10-03 06:11 UTCpass0daily-2026-10-03
2026-10-02 15:24 UTCpass0daily-2026-10-02
2026-10-01 08:14 UTCpass0daily-2026-10-01
2026-09-30 07:35 UTCpass0daily-2026-09-30
2026-09-29 19:50 UTCfail1daily-2026-09-29
2026-09-28 09:22 UTCpass0daily-2026-09-28
2026-09-25 21:20 UTCpass0daily-2026-09-25
2026-09-23 06:53 UTCpass0daily-2026-09-23
2026-09-22 07:05 UTCpass0daily-2026-09-22
2026-09-21 07:28 UTCpass0daily-2026-09-21
2026-09-19 05:30 UTCpass0daily-2026-09-19
2026-09-18 13:56 UTCpass0daily-2026-09-18
2026-09-17 05:23 UTCpass0daily-2026-09-17
2026-09-16 05:22 UTCpass0daily-2026-09-16
2026-09-15 05:39 UTCpass0daily-2026-09-15
2026-09-14 05:13 UTCpass0daily-2026-09-14
2026-09-13 05:09 UTCpass0daily-2026-09-13
2026-09-12 07:25 UTCpass0daily-2026-09-12
2026-09-11 11:09 UTCpass0daily-2026-09-11

Registry presence

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

  1. absence from Coinbase confirmed, rule v1
  2. absent from Coinbase at this pull
  3. listed in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-09-10 06:18 UTC · method

The input and output block
{
  "input": {
    "type": "http",
    "method": "GET",
    "pathParams": {
      "entity_id": "320193"
    }
  },
  "output": {
    "type": "json",
    "example": {
      "as_of": "2026-09-10T00:00:00Z",
      "entity": {
        "cik": "0000320193",
        "name": "Example"
      },
      "source": "SEC EDGAR",
      "filings": [],
      "decision": "available",
      "limitations": [],
      "facts_summary": {},
      "disclosure_signals": []
    }
  }
}
Cite this page

This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "entities filing risk snapshot on api.jpverify.com". https://tollindex.com/e/api-jpverify-com-v1-entities-entity-id-filing-risk-snapshot-8061b4. Accessed [access date].

BibTeX

@misc{toll-e-api-jpverify-com-v1-entities-entity-id-filing-risk-snapshot-8061b4-2026-11-01,
  author = {TOLL},
  title = {entities filing risk snapshot on api.jpverify.com},
  howpublished = {\url{https://tollindex.com/e/api-jpverify-com-v1-entities-entity-id-filing-risk-snapshot-8061b4}},
  year = {2026},
  month = {11},
  note = {Frozen at its last observation, 2026-11-01 21:59 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 entities filing risk snapshot, 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 8061b4be450b4bccb13304d016c1d55d47fb6703b999faa93078d69a6541adae from wallet 0xe4A4E5B226bE71e7b6eD523bc7a91089c770572F

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

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