x402 List Submit a serviceSubmit
Menu

JPVerify

payment-readyonline

payment-ready until 2026-11-15

Japanese business document OCR and public-registry verification: receipt, invoice and business-card extraction, corporate-number and qualified-invoice (T-number) checks against NTA public data, and Japanese address normalization; 24 paid routes at $0.001–$0.10 USDC per call on Base mainnet, with invalid input rejected with HTTP 422 before payment.

www.jpverify.com ↗

Call it x402 v2

x402 v2

Base URL
https://api.jpverify.com
Payment
x402 v2, header channel
$ curl -i -X POST 'https://api.jpverify.com/v1/invoices/counterparty-check'

An unpaid request returns HTTP 402 with the payment terms. Sign a payment authorization, then retry with the PAYMENT-SIGNATURE header.

Endpoints 1 paid route on api.jpverify.com

POST/v1/invoices/counterparty-checkBase$0.05since 11-07

Prices as captured in the 402 response: $0.05, unchanged since first capture.

Example 402 response

Endpoints and prices

Current paid endpoints; minimum quoted prices in USD where available; first capture dates in UTC
MethodPathDescriptionPriceNetworkAsset402 channelCaptured
POST/v1/invoices/counterparty-checkCheck a known EU VAT ID and/or Peppol participant using separate tax-validity, entity-match, and discoverability evidence. VIES is never used for name search and upstream responses are not resold. / 既知のEU VAT IDまたはPeppol参加者を税番号有効性・法人一致・到達性に分けて確認します。VIESは名称検索に使わず、元データは再販しません。$0.05BaseUSDCheadersince 11-07

Payment evidence

402 payload captured at . Check evidence JSON · Measurement methodology.

1 payload captured by the monitor.

194 lines, scroll inside

{
  "error": "Payment required",
  "accepts": [
    {
      "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "extra": {
        "name": "USD Coin",
        "version": "2"
      },
      "payTo": "0xe4A4E5B226bE71e7b6eD523bc7a91089c770572F",
      "amount": "50000",
      "scheme": "exact",
      "network": "eip155:8453",
      "maxTimeoutSeconds": 300
    }
  ],
  "resource": {
    "url": "https://api.jpverify.com/v1/invoices/counterparty-check",
    "tags": [
      "invoice",
      "vat",
      "vies",
      "peppol",
      "evidence"
    ],
    "mimeType": "application/json",
    "description": "Check a known EU VAT ID and/or Peppol participant using separate tax-validity, entity-match, and discoverability evidence. VIES is never used for name search and upstream responses are not resold. / 既知のEU VAT IDまたはPeppol参加者を税番号有効性・法人一致・到達性に分けて確認します。VIESは名称検索に使わず、元データは再販しません。",
    "serviceName": "Cross-Border Invoice Counterparty Check"
  },
  "extensions": {
    "bazaar": {
      "info": {
        "input": {
          "body": {
            "vat_id": "DE123456789",
            "participant_id": "iso6523-actorid-upis::0088:123456789",
            "response_language": "both"
          },
          "type": "http",
          "method": "POST",
          "bodyType": "json"
        },
        "output": {
          "type": "json",
          "example": {
            "vat": {
              "status": "valid"
            },
            "checks": [],
            "peppol": {
              "status": "discoverable"
            },
            "decision": "verified",
            "conflicts": [],
            "entity_match": {
              "status": "not_requested"
            }
          }
        }
      },
      "schema": {
        "type": "object",
        "$schema": "https://json-schema.org/draft/2020-12/schema",
        "required": [
          "input"
        ],
        "properties": {
          "input": {
            "type": "object",
            "required": [
              "type",
              "method",
              "bodyType",
              "body"
            ],
            "properties": {
              "body": {
                "type": "object",
                "anyOf": [
                  {
                    "required": [
                      "vat_id"
                    ]
                  },
                  {
                    "required": [
                      "participant_id"
                    ]
                  }
                ],
                "properties": {
                  "name": {
                    "type": "string",
                    "maxLength": 300
                  },
                  "vat_id": {
                    "type": "string",
                    "maxLength": 32,
                    "description": "Known EU VAT ID; VIES does not support name search."
                  },
                  "country_code": {
                    "type": "string",
                    "maxLength": 2,
                    "minLength": 2
                  },
                  "participant_id": {
                    "type": "string",
                    "maxLength": 120,
                    "description": "Qualified Peppol participant identifier in scheme::value form; known legacy ISO 6523 scheme:value is normalized server-side."
                  },
                  "response_language": {
                    "enum": [
                      "ja",
                      "en",
                      "both"
                    ],
                    "type": "string",
                    "default": "both",
                    "description": "Response presentation language: ja, en, or both. / レスポンス表示言語: ja（日本語）、en（英語）、both（両方）。"
                  }
                },
                "additionalProperties": false
              },
              "type": {
                "type": "string",
                "const": "http"
              },
              "method": {
                "enum": [
                  "POST",
                  "PUT",
                  "PATCH"
                ],
                "type": "string"
              },
              "bodyType": {
                "enum": [
                  "json",
                  "form-data",
                  "text"
                ],
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "output": {
            "type": "object",
            "required": [
              "type"
            ],
            "properties": {
              "type": {
                "type": "string"
              },
              "example": {
                "vat": {
                  "type": "object"
                },
                "type": "object",
                "checks": {
                  "type": "array",
                  "items": {
                    "type": "object"
                  }
                },
                "peppol": {
                  "type": "object"
                },
                "decision": {
                  "type": "string"
                },
                "conflicts": {
                  "type": "array",
                  "items": {
                    "type": "object"
                  }
                },
                "checked_at": {
                  "type": "string",
                  "format": "date-time"
                },
                "entity_match": {
                  "type": "object"
                }
              }
            }
          }
        }
      }
    }
  },
  "x402Version": 2
}

Can I trust it score from our own monitoring

score from our own monitoring

90/100 Solid

#15 of 187 in Verification. Bands: strong 93+, solid 75+, mixed 55+, weak below 55.

Reliability
100% uptime since 11-07
Compliance
A 14/14 checks pass
Price
$0.05 p82 in Verification
Risk
clean no risk flag
Traction
---
14/14 compliance checks
  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

402 terms unchanged since 2026-11-07. Last up 2026-11-08.

── Site signals

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
How the score works

What the score read on this service: status online, 100% uptime, latest daily rollup (no 30d window yet), 1058ms response p95, x402 compliance 14 of 14, $0.05 price against the category. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

It is a score inside Verification, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 187 listings, this one among them: the same 187 the position above is counted against. When the two differ, the field is the wider one, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

All measured facts

What it does

Japanese business document OCR and public-registry verification: receipt, invoice and business-card extraction, corporate-number and qualified-invoice (T-number) checks against NTA public data, and Japanese address normalization; 24 paid routes at $0.001–$0.10 USDC per call on Base mainnet, with invalid input rejected with HTTP 422 before payment. Example: POST /jp-company/verify {"corporate_number":"1010001008846"}.

JPVerify is a listed x402 Verification API. Captured payment terms name Base. Monitoring and settlement figures below describe the observations available to this directory; an unpaid HTTP 402 check does not prove that a paid call will deliver.

Assessment computed at . Latest service check observed at . Service data JSON · Measurement methodology.

Page rendered at . This response time is separate from the observation and computation times attached to each measurement.

Latest endpoint observation: . Latest price capture: . Prices are recorded quotes, not a promise of availability. Token assets and payment terms are listed separately. Endpoint data JSON · Price history JSON · Measurement methodology.

Assessment computed at . Uptime uses the stated daily-rollup window; response times are in milliseconds, compliance is passed/evaluated checks, and traction is a measured settlement floor. The comparison score is out of 100 within this category. Assessment JSON · Measurement methodology.

Observed daily coverage: 2026-10-10 to 2026-11-08 UTC. Daily monitoring and settlement rollups do not expose their computation time; a bucket date is not an update timestamp. Uptime and response JSON · Volume JSON · Buyers JSON · Measurement methodology.

Ranked from the measured category pool, refreshed at most once a minute. The comparison has no persisted computation timestamp; the assessment time above belongs to this service only. Ranking API documentation · Ranking methodology.

x402 List home · Services · Verification

uptime · latest daily rollup
-
uptime 7d
-
uptime 30d
-
uptime 90d
-
response p95
1058ms
avg response
1058ms
total checks
1

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

price (min)
$0.05
category percentile (min)
p82 in Verification
endpoints / prices
1 / 1
model
flat
stability
100%

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
83d
registrar
Cloudflare, Inc.
hosting
custom
domain created
2026-08-16

Identity facts, not a risk score.

On-chain traction has not been assessed for this service yet.

member since
2026-11-07
Recent checks
Latest 12 unpaid HTTP checks, newest first; response times in milliseconds, observation times in UTC
Checked at (UTC)StatusHTTPResponseEndpoints
Online402786ms1
Online4021132ms1
Online402858ms1
Online402855ms1
Online4021313ms1
Online4021478ms1
Online4021338ms1
Online402941ms1
Online402965ms1
Online402791ms1
Online4021140ms1
Online4021058ms1

Changes0 in 30d

No changes recorded in the last 30 days.

all changes

Over time

On-chain volume

On-chain traction has not been assessed for this service yet.

Uptime 100% on all 1 completed day
Uptime
100% on all 1 completed day

On-chain traction has not been assessed for this service yet.

More charts
Response time daily average, ms min 1039ms, avg 1082ms, max 1126ms

10-10 to 11-08* UTC

Each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/jpverify/price, /scores, /volume and /buyers.

Values

* today so far, partial (UTC).

The uptime summary counts completed UTC days only. The strip, readouts and table retain today's partial reading.

Assessment history last recorded at . Each UTC day uses its last recorded run; missing readings stay unmeasured. Assessment history JSON · Measurement methodology.

Daily values, 2026-11-07 to 2026-11-08: uptime percent, average response milliseconds, compliance passed/total, price percentile 0-100, site signals out of 6; UTC dates
DayUptimeResponseCompliancePrice percentileSite signals
2026-11-07100%1038.83ms14/14p825/6
2026-11-08*100%1126.00msno datano datano data

Alternatives in Verification

agentshield.live facts strong 99/100 99.9% up 30d --- 30d
GL1TCH Token Safety API strong 96/100 100% up 30d --- 30d
Apex Pay · verified agent tools strong 96/100 99.9% up 30d --- 30d
PaywallWatch strong 96/100 100% up 30d --- 30d
how.is strong 95/100 99.9% up 30d --- 30d

5 of 186 other ranked services in Verification, ordered by the same measured score.

Own this service?

Keep this listing accurate. Ownership is proven with a domain check and every change is reviewed by hand.

Update this listing

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

Verify this service ($0.25)
Embed a badge

HTML

<a href="https://x402-list.com/services/jpverify?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/jpverify.svg" alt="JPVerify listed on x402-list" height="28">
</a>

Markdown

[![JPVerify on x402-list](https://x402-list.com/badge/jpverify.svg)](https://x402-list.com/services/jpverify?utm_source=badge&utm_medium=referral&utm_campaign=embed)

HTML, live uptime variant

<a href="https://x402-list.com/services/jpverify?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/jpverify.svg?data=uptime" alt="JPVerify uptime on x402-list" height="28">
</a>
Delisting

To request delisting, email info@x402-list.com with the service name, slug, or URL. Removal is free and does not require proof of ownership. See all free email requests.