passlisted in Coinbase#6 by calls of 18 on this host
0.03 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-28 09:06 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.03 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 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.
api.jpverify.com lists 18 endpoints; jp regulated entity verify is tied 6th by calls with 12 others.
Callers of jp regulated entity verify supply a json body with the fields categories, corporate_number and response_language.
A response from jp regulated entity verify, as declared, includes decision, licenses, warnings, identity_match, license_status, coverage_status and 1 other.
jp regulated entity verify drew a single call from a single payer in the trailing 30 days.
The last call to jp regulated entity verify came 18 days before the snapshot, 2026-08-28.
The declared price is 0.03 USDC on Base.
jp regulated entity verify takes 4% of the calls counted across api.jpverify.com.
api.jpverify.com serves jp regulated entity verify, a POST endpoint that TOLL places in identity, listed in the Coinbase registry.
jp regulated entity verify answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to jp regulated entity verify within identity: address risk at vibesprings.net and company research at lionx402.com.
jp regulated entity verify is priced above 75% of comparable listings in identity.
18 listed endpoints on one host pay to the same wallet.
The seller's tags on jp regulated entity verify are japan, fsa, licensing and verification.
Exactly this price appears on 51 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.03 USDC | exact | 0xe4A4E5…70572F |
the checks, as of 2026-09-15 05:29 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 05:29 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:03 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:59 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:15 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 10:56 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-28 09:06 UTC · method · live
The input and output block
{
"input": {
"body": {
"categories": [
"funds_transfer_business"
],
"corporate_number": "1234567890123",
"response_language": "en"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"decision": "verified",
"licenses": [],
"warnings": [],
"identity_match": "exact",
"license_status": "licensed",
"coverage_status": "covered",
"source_freshness": "fresh"
}
}
}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 regulated entity verify on api.jpverify.com", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/api-jpverify-com-jp-regulated-entity-verify-71a19c/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-api-jpverify-com-jp-regulated-entity-verify-71a19c-2026-09-15T16-57Z,
author = {TOLL},
title = {jp regulated entity verify on api.jpverify.com},
howpublished = {\url{https://tollindex.com/e/api-jpverify-com-jp-regulated-entity-verify-71a19c/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.