TOLL

What software pays for, recorded every six hours.

Snapshot
2026-10-12 15:20 UTC
Sweep
daily-2026-10-12 · finished 2026-10-12 13:00 UTC
Listed
33,498

jp address validate derived

api.jpverify.comOtherderived

POST https://api.jpverify.com/jp-address/validate

passlisted in Coinbase#3 by calls of 6 on this host

0.005 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-12 15:20 UTC · method · pinnable

Validation state
pass
as of 2026-10-12 07:16 UTC · method · pinnable · sweep daily-2026-10-12
Uptime, 7 / 30 / 90 days
100% / 100% / 100%
as of 2026-10-12 07:16 UTC · method · pinnable · 7 of 7 in 7d, 27 of 27 in 30d, 29 of 29 in 90d
Calls, trailing 30 days
1
as of 2026-10-12 15:20 UTC · method · pinnable
Unique payers, trailing 30 days
1
as of 2026-10-12 15:20 UTC · method · pinnable
Last called
2026-10-09 07:23 UTC
as of 2026-10-12 15:20 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.005 USDC
as of 2026-10-12 15:20 UTC · method · pinnable · on eip155:8453
Networks
1
as of 2026-10-12 15:20 UTC · method · pinnable

Counters

120 observations, 4 of them a change

How has the volume on this endpoint moved?

12110 Sep11 Sep12 Sep13 Sep14 Sep15 Sep16 Sep17 Sep18 Sep19 Sep20 Sep21 Sep22 Sep23 Sep24 Sep25 Sep26 Sep27 Sep28 Sep29 Sep30 Sep1 Oct2 Oct3 Oct4 Oct5 Oct6 Oct7 Oct8 Oct9 Oct10 Oct11 Oct12 Oct
Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-10. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot.

In words

api.jpverify.com serves jp address validate, a POST endpoint that TOLL places in the "other" category, listed in the Coinbase registry.

A call to jp address validate costs 0.005 USDC on Base, as declared.

Callers of jp address validate supply a json body with the fields strict, address and required_level.

jp address validate returns json; the example shows reasons, warnings, confidence, granularity, match_level, match_status and 2 others.

jp address validate answered the sweep of 2026-10-12 with a valid 402, as at every sweep since 2026-09-11.

jp address validate is one of 6 listed endpoints on api.jpverify.com, tied 3rd by calls with 3 others among them.

jp address validate takes 13% of the calls counted across api.jpverify.com.

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

jp address validate was last called 3 days before the snapshot.

Closest in price to jp address validate within the "other" category: enrich profile at win.oneshotagent.com and ping at www.api-xpay.com.

jp address validate is priced above 31% of comparable listings in the "other" category.

The wallet paid by jp address validate is the payee of 18 endpoints on one host.

The seller's own tags are japan, address, validation and quality.

The price of jp address validate is declared by 770 other listings in the "other" category too.

Payment options as declared

the payment options, as of 2026-10-12 15:20 UTC · method · pinnable

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

Preflight checks at the last sweep

the checks, as of 2026-10-12 07:16 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-10-12 07:16 UTCpass0daily-2026-10-12
2026-10-11 05:41 UTCpass0daily-2026-10-11
2026-10-10 13:57 UTCpass0daily-2026-10-10
2026-10-09 05:59 UTCpass0daily-2026-10-09
2026-10-08 07:43 UTCpass0daily-2026-10-08
2026-10-07 06:56 UTCpass0daily-2026-10-07
2026-10-06 07:44 UTCpass0daily-2026-10-06
2026-10-05 07:11 UTCpass0daily-2026-10-05
2026-10-04 09:53 UTCpass0daily-2026-10-04
2026-10-03 04:53 UTCpass0daily-2026-10-03
2026-10-02 14:08 UTCpass0daily-2026-10-02
2026-10-01 07:12 UTCpass0daily-2026-10-01
2026-09-30 06:29 UTCpass0daily-2026-09-30
2026-09-29 18:49 UTCpass0daily-2026-09-29
2026-09-28 05:35 UTCpass0daily-2026-09-28
2026-09-25 20:22 UTCpass0daily-2026-09-25
2026-09-23 06:01 UTCpass0daily-2026-09-23
2026-09-22 06:11 UTCpass0daily-2026-09-22
2026-09-21 06:34 UTCpass0daily-2026-09-21
2026-09-20 19:13 UTCpass0daily-2026-09-20
2026-09-19 04:34 UTCpass0daily-2026-09-19
2026-09-18 10:26 UTCpass0daily-2026-09-18
2026-09-17 04:32 UTCpass0daily-2026-09-17
2026-09-16 04:33 UTCpass0daily-2026-09-16
2026-09-15 04:30 UTCpass0daily-2026-09-15
2026-09-14 04:27 UTCpass0daily-2026-09-14
2026-09-13 04:25 UTCpass0daily-2026-09-13
2026-09-12 06:41 UTCpass0daily-2026-09-12
2026-09-11 10:13 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-10-09 07:23 UTC · method · live

The input and output block
{
  "input": {
    "body": {
      "strict": false,
      "address": "東京都千代田区千代田1丁目1番1号",
      "required_level": 8
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "reasons": [
        "provider_level_below_requested_level"
      ],
      "warnings": [],
      "confidence": 0.79,
      "granularity": "block",
      "match_level": 7,
      "match_status": "partial",
      "parsed_level": 8,
      "verified_level": 7,
      "requested_level": 8,
      "parse_confidence": 0.99,
      "validation_scope": "hierarchy_and_evidence_consistency",
      "address_validated": false,
      "postal_code_match": null,
      "postal_confidence": null,
      "validation_source": "parser + Jageocoder local dictionary",
      "precision_satisfied": false,
      "geographic_match_confidence": 0.8
    }
  }
}
Cite this page

The pinned URL below renders this page from the snapshot of 2026-10-12 15:20 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 address validate on api.jpverify.com", snapshot of 2026-10-12 15:20 UTC. https://tollindex.com/e/api-jpverify-com-jp-address-validate-3d9223/at/2026-10-12T15-20Z. Accessed [access date].

BibTeX

@misc{toll-e-api-jpverify-com-jp-address-validate-3d9223-2026-10-12T15-20Z,
  author = {TOLL},
  title = {jp address validate on api.jpverify.com},
  howpublished = {\url{https://tollindex.com/e/api-jpverify-com-jp-address-validate-3d9223/at/2026-10-12T15-20Z}},
  year = {2026},
  month = {10},
  note = {Pinned view of the snapshot of 2026-10-12 15:20 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 jp address validate, 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 3d922315b3f8283551e0e9d649502953fc5e2214ca4bbb77b62e71ea6ca9e9eb from wallet 0xe4A4E5B226bE71e7b6eD523bc7a91089c770572F

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

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