passabsent from every registry#3 by calls of 6 on this host
0.01 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-15 21:20 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / — / 83%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-16 23:54 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
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 29 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.
TOLL files jp invoice verify under identity: a POST endpoint on api.jpverify.com, listed in neither registry at the last pull.
On Base, jp invoice verify asks 0.01 USDC per call.
The request to jp invoice verify is a json body with the fields response_language and registration_number.
A response from jp invoice verify, as declared, includes name, entity, source, status, address, verdict and 2 others.
jp invoice verify answered the sweep of 2026-09-16 with a valid 402, passing 5 of 6 sweeps since 2026-09-11.
jp invoice verify shares api.jpverify.com with 5 other listed endpoints and is tied 3rd by calls with 4 others.
jp invoice verify takes 13% of the calls counted across api.jpverify.com.
In the trailing 30 days: one call, one payer.
jp invoice verify was last called 58 days before the snapshot.
Closest in price to jp invoice verify within identity: verify job at livecheck.fly.dev and screening match at api.relaystation.ai.
jp invoice verify is priced above 34% of comparable listings in identity.
The wallet paid by jp invoice verify is the payee of 18 endpoints on one host.
The seller's tags on jp invoice verify are japan, invoice, t-number and nta.
jp invoice verify was missing from the Coinbase registry at the pull of 2026-09-16, confirmed at the pull of 2026-09-16; that is registry presence, not liveness.
The price of jp invoice verify is declared by 707 other listings in identity 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.
the payment options, as of 2026-09-15 21:20 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0xe4A4E5…70572F |
the checks, as of 2026-09-16 04:40 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-16 04:40 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 04:38 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:34 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:32 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:48 UTC | fail | 1 | daily-2026-09-12 |
| 2026-09-11 10:21 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-16 23:54 UTC · method
The input and output block
{
"input": {
"body": {
"response_language": "both",
"registration_number": "T1013301046627"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"name": "株式会社ABC",
"entity": "corporation",
"source": "Japan National Tax Agency Invoice System",
"status": "registered",
"address": "東京都千代田区千代田1-1",
"verdict": "qualified",
"data_as_of": "2026-07-31",
"cancel_date": null,
"format_valid": true,
"record_found": true,
"checksum_valid": true,
"data_freshness": "monthly_snapshot",
"registered_name": "株式会社ABC",
"corporate_number": "1013301046627",
"registration_date": "2023-10-01",
"registration_number": "T1013301046627",
"qualified_invoice_registered": true
}
}
}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, "jp invoice verify on api.jpverify.com". https://tollindex.com/e/api-jpverify-com-jp-invoice-verify-4829ec. Accessed [access date].
BibTeX
@misc{toll-e-api-jpverify-com-jp-invoice-verify-4829ec-2026-10-13,
author = {TOLL},
title = {jp invoice verify on api.jpverify.com},
howpublished = {\url{https://tollindex.com/e/api-jpverify-com-jp-invoice-verify-4829ec}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.