passlisted in Coinbase#6 by calls of 18 on this host
0.05 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- 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.05 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 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.
api.jpverify.com lists 18 endpoints; jp company verify batch is tied 6th by calls with 12 others.
Callers of jp company verify batch supply a json body with the fields items and response_language.
Its example response has the fields count and results.
jp company verify batch drew a single call from a single payer in the trailing 30 days.
The last call to jp company verify batch came 30 days before the snapshot, 2026-08-16.
On Base, jp company verify batch asks 0.05 USDC per call.
Of the calls counted across api.jpverify.com, jp company verify batch takes 4%.
jp company verify batch, a POST endpoint on api.jpverify.com, appears in the Coinbase registry; TOLL's taxonomy puts it in identity.
jp company verify batch answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to jp company verify batch within identity: attest at agent402.tools and domain reputation at api.strale.io.
jp company verify batch is priced above 80% of comparable listings in identity.
Its payee wallet receives for 18 listed endpoints on one host.
The seller's tags on jp company verify batch are japan, company, corporate-number and batch.
Exactly this price appears on 78 other listings in identity.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.05 USDC | exact | 0xe4A4E5…70572F |
the checks, as of 2026-09-15 04:14 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-15 04:14 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:12 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:11 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:27 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 09:55 UTC | pass | 0 | daily-2026-09-11 |
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-08-16 23:54 UTC · method · live
The input and output block
{
"input": {
"body": {
"items": [
{
"corporate_number": "1180301018771"
}
],
"response_language": "both"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"count": 1,
"results": [
{
"status": "active",
"verified": true
}
]
}
}
}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, "jp company verify batch on api.jpverify.com", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-jpverify-com-jp-company-verify-batch-2715fe/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-api-jpverify-com-jp-company-verify-batch-2715fe-2026-09-15T16-57Z,
author = {TOLL},
title = {jp company verify batch on api.jpverify.com},
howpublished = {\url{https://tollindex.com/e/api-jpverify-com-jp-company-verify-batch-2715fe/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].}
}None yet. Anything submitted through the form below is published here with its outcome.