Back to directory

api.jpverify.com

https://api.jpverify.com
● healthy general

Japanese postal-code lookup and reverse lookup. Keywords: Japanese postal lookup, Japan Post postal code, postal code reverse lookup, 日本郵便番号検索. Use a postal code or prefecture/city/ward/town components against the local Japan Post snapshot. / 通过邮编或都道府县、市区町村、区、町名字段,在本地 Japan Post 数据中进行日本邮编反查。

Category
general
Chains
eip155:8453
Price
$0.0010–$0.0050 USDC

Quality grade

How grading works
B+ 68.8 / 100
Availability 20.0 / 20
Endpoint responded (HTTP 200)
Payability 15.0 / 15
  • ✓ Answers a real HTTP 402 challenge
  • ✓ Publishes a /.well-known/x402 descriptor
  • ✓ Payment address on record
  • ✓ Settlement network declared
  • ✓ Price declared
Demand 15.2 / 35
14 distinct payers, 121 USDC transfers in the last 30 days
Performance 5.6 / 10
Last probe answered in 999 ms (full marks at 200 ms or less)
Readiness 13.0 / 15
Agent readiness 87/100
Owner verified 0.0 / 5
Nobody has claimed this listing yet
Endpoint last checked 18 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 68.8/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements 10/10 Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge 20/25 Endpoint reachable; its 402 challenge was seen earlier (999 ms).
x402 version n/a x402 version not observed yet.
Signed descriptor n/a No x402 standard defines a signed descriptor.
Uptime (30 days) 15/15 32/32 probes succeeded over 30 days (100%).
Resource declaration 10/10 Declares 18 paid resource(s).
Verified identity 5/10 Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags 5/5 seen in a source within 7 days; declares x402.
Security declaration n/a Payment is the access control for an x402 resource.
Applicable criteria total 75 points, scaled to 100.
Responsiveness: Responsive (999 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, bazaar_feed. Qualifies the payment claim; adds no points.
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 75% of peers
This listing 87 · peer median 78
Latency
Faster than 6% of peers
This listing 999 ms · peer median 205 ms

Where it loses the most points, and how to win them back

  • Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
    Now: Endpoint reachable; its 402 challenge was seen earlier (999 ms).
  • Verified identity −5 — Claim the listing and prove control of its domain.
    Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.

How many agent tools actually work · All statistics

Paid endpoints

18 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

POST https://api.jpverify.com/v1/batch-jobs

Create a paid asynchronous structured batch job. Price is the exact per-operation unit price multiplied by validated item count; results are available only after settlement. / 構造化データを非同期で一括処理する有料ジョブを作成します。料金は操作別単価と検証済み件数の積で、結果は決済完了後に取得できます。

POST https://api.jpverify.com/v1/jp/companies/verify

Japanese company verification. Keywords: company verification Japan, corporate number, 法人番号, 法人番号照合, 日本企業. Resolve a company name, 13-digit corporate number (法人番号), or address against Japan's NTA corporate registry; return active/closed status and match evidence. / 会社名、13桁の法人番号、住所を国税庁の法人番号公表データと照合し、

POST https://api.jpverify.com/v1/jp/companies/report

Japanese company KYB pre-check: NTA identity, status and risk flags, plus capital, employees, website (gBizINFO/Wikidata), listing and latest EDINET filing, FSA licences and former names. Keywords: company report Japan, 法人番号. Not full KYC/KYB. / 法人番号・法人名・住所・状態・リスクに加え、資本金・従業員数・Webサイト・上場情報・金融庁登録・旧商号を返

POST https://api.jpverify.com/v1/jp/suppliers/resolve

Resolve a Japanese supplier using combined company, qualified-invoice, and address evidence. gBizINFO v2 may add projected activity evidence inside this response as optional enrichment; it is not a standalone data-resale endpoint. Returns coverage-aware checks without making a legal KYB conclusion.

POST https://api.jpverify.com/v1/jp/addresses/normalize

Japanese address normalization (日本住所正規化, 住所標準化). Parse an address with or without a postal code into prefecture/city/components and match it against local address data. A unique truncated town prefix may be recovered; ambiguous prefixes are not guessed. A missing postal code is not inferred; use pos

POST https://api.jpverify.com/v1/jp/addresses/parse

Japanese address parser that splits an address into components. Keywords: Japanese address parser, address components, chome, block, lot, house, 丁目, 番地, 号. Parse a Japanese address into components without returning postal validation or geocoding; local postal prefix evidence may safely recover a uni

POST https://api.jpverify.com/v1/jp/postal-codes/lookup

Japanese postal-code lookup and reverse lookup. Keywords: Japanese postal lookup, Japan Post postal code, postal code reverse lookup, 日本郵便番号検索. Use a postal code or prefecture/city/ward/town components against the local Japan Post snapshot. / 郵便番号、または都道府県・市区町村・区・町域を指定し、ローカルの日本郵便データで郵便番号を検索・逆引きします。

POST https://api.jpverify.com/v1/jp/addresses/geocode

Japanese forward geocoding from an address to coordinates. Keywords: Japan geocoder, address to coordinates, building-level geocode, Jageocoder, chome, block, lot, house. Returns provider-neutral local candidates, coordinates, address IDs, hierarchy levels, unmatched tails, and partial-match warning

POST https://api.jpverify.com/v1/jp/addresses/validate

Japanese address validation and quality decision. Keywords: Japanese address validation, address conflict, address quality, partial match, 日本住所検証. Validate parser, postal, and geocoder evidence using one address policy, returning exact, partial, ambiguous, conflict, or unverified status with the acc

POST https://api.jpverify.com/v1/jp/invoice-registrations/verify

Japanese qualified-invoice verification. Keywords: T-number validation, qualified invoice, 適格請求書, インボイス登録番号, T番号. Validate a T+13 digit registration number against Japan's NTA registry and return registered, cancelled, or not-found status, corporate number, and dates. / T+13桁の適格請求書登録番号を国税庁データと照合し、登録

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

Japanese invoice issuer check. Keywords: invoice issuer check, 適格請求書, インボイス登録番号, T番号, 登録取消. Checks that the T-number is registered, that it belongs to the issuer name (and address, if given) on the invoice, that the issuer was registered on the invoice date and not cancelled or expired, and (optiona

POST https://api.jpverify.com/v1/jp/companies/verify-batch

Batch Japanese company verification / 日本企業法人番号一括検証: verify up to 100 company names, corporate numbers, or addresses against Japan's NTA registry in one paid request, at $0.008 per item. Results preserve input order and expose per-item index, error, and retryable metadata. / 1回の有料リクエストで最大100件の会社名・法人番

POST https://api.jpverify.com/v1/jp/invoice-registrations/verify-batch

Batch Japanese qualified-invoice verification. Keywords: batch T-number verification, インボイス登録番号一括検証, 適格請求書. Verify up to 100 T+13 digit invoice registration numbers against Japan's NTA registry for accounting and AP workflows, at $0.008 per item. Results preserve input order and expose per-item inde

POST https://api.jpverify.com/v1/jp/invoices/check-issuer-batch

Batch Japanese invoice issuer check (請求書一括確認). Up to 100 invoices per paid request, $0.04 each: T-number registered, issuer name (and address), registration on the invoice date, optional supplier master number. Results keep input order with per-item index, error and retryable. / 最大100件の請求書の発行者を1回で確認

POST https://api.jpverify.com/v1/jp/regulated-entities/verify

Verify a Japanese FSA-regulated entity across the three V1 covered categories. / 日本の金融庁対象三分類で法人を照合します。

GET https://api.jpverify.com/v1/jp/filings

Search EDINET filing metadata with official evidence references. / 公式根拠付きでEDINET提出書類を検索します。

POST https://api.jpverify.com/v1/jp/companies/resolve

Identify a Japanese company from an English or brand name with an English address, postal code or prefecture, a website/e-mail domain, or a T-number, corporate number, LEI or securities code. Identifiers resolve exactly; a name alone returns candidates. Returns, in English, the legal Japanese name,

POST https://api.jpverify.com/v1/jp/invoices/validate-pint

Validate JP PINT 1.1.3 Invoice XML against pinned offline OASIS UBL 2.1 XSD and OpenPeppol Schematron, with optional NTA issuer evidence. document_valid is the official XSD/Schematron result; decision and trusted are separate registry-aware fields. It is an evidence check, not tax/legal or Peppol co

How to call

cURL · x402-fetch / x402-axios will auto-handle 402
curl -sS -i -X GET https://api.jpverify.com  # expect HTTP 402 Payment Required (about $0.001/call)
/.well-known/x402.json
https://api.jpverify.com/.well-known/x402

Listed in

Directories this entry was found in.

cdp-bazaar since 2026-08-16