TOLL

What software pays for, recorded every six hours.

Snapshot
2026-09-15 16:57 UTC
Sweep
daily-2026-09-15 · finished 2026-09-15 07:10 UTC
Listed
16,167

invoices counterparty check derived

api.jpverify.comSearchderived

POST https://api.jpverify.com/v1/invoices/counterparty-check

passlisted in Coinbase#6 by calls of 18 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-09-15 16:57 UTC · method · pinnable

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

Counters

28 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 1,632 endpoints in Search 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: 980 in the category are counted higher and 651 lower.

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

invoices counterparty check is one of 18 listed endpoints on api.jpverify.com, tied 6th by calls with 12 others among them.

invoices counterparty check takes a json body with the fields vat_id, participant_id and response_language.

A response from invoices counterparty check, as declared, includes vat, checks, peppol, decision, conflicts and entity_match.

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

invoices counterparty check was last called 5 days before the snapshot.

Each call is priced at 0.05 USDC, payable on Base.

invoices counterparty check takes 4% of the calls counted across api.jpverify.com.

At api.jpverify.com, invoices counterparty check takes POST requests, is listed in the Coinbase registry, and falls under search by TOLL's rules.

invoices counterparty check answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.

Closest in price to invoices counterparty check within search: serp at api.kadec0.xyz and trend at google-trends.use.x402atlas.com.

Among comparable prices in search, invoices counterparty check sits above 78% of them.

The payee wallet is shared by 18 listings on one host.

The seller's tags on invoices counterparty check are invoice, vat, vies and peppol.

The price of invoices counterparty check is declared by 74 other listings in search too.

Payment options as declared

the payment options, as of 2026-09-15 16:57 UTC · method · pinnable

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-09-15 06:14 UTC · method · pinnableendpoint 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-09-15 06:14 UTCpass0daily-2026-09-15
2026-09-14 05:45 UTCpass0daily-2026-09-14
2026-09-13 05:38 UTCpass0daily-2026-09-13
2026-09-12 07:55 UTCpass0daily-2026-09-12
2026-09-11 11:49 UTCpass0daily-2026-09-11

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-09-10 06:18 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "vat_id": "DE123456789",
      "participant_id": "iso6523-actorid-upis::0088:123456789",
      "response_language": "both"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "vat": {
        "status": "valid"
      },
      "checks": [],
      "peppol": {
        "status": "discoverable"
      },
      "decision": "verified",
      "conflicts": [],
      "entity_match": {
        "status": "not_requested"
      }
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "invoices counterparty check on api.jpverify.com", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-jpverify-com-v1-invoices-counterparty-check-b1b737/at/2026-09-15T16-57Z. Accessed [access date].

BibTeX

@misc{toll-e-api-jpverify-com-v1-invoices-counterparty-check-b1b737-2026-09-15T16-57Z,
  author = {TOLL},
  title = {invoices counterparty check on api.jpverify.com},
  howpublished = {\url{https://tollindex.com/e/api-jpverify-com-v1-invoices-counterparty-check-b1b737/at/2026-09-15T16-57Z}},
  year = {2026},
  month = {9},
  note = {Pinned view of the snapshot of 2026-09-15 16:57 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 invoices counterparty check, 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 b1b7373da095a443440033c5d8fd0495c6edd57c610a8a53097d2ed5f15304b8 from wallet 0xe4A4E5B226bE71e7b6eD523bc7a91089c770572F

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

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