Validate Japanese Peppol e-invoices (JP PINT 1.1.3 UBL Invoice XML) with JPVerify against the official OASIS UBL 2.1 XSD and OpenPeppol JP PINT Schematron, optionally checking the seller's qualified-invoice T-number in the National Tax Agency registry. Use when a task involves checking a JP PINT / Peppol (デジタルインボイス) XML invoice before sending it, accepting it into accounting, or paying it. Paid per call (API key credits or x402).
JP PINT e-invoice validation / JP PINT デジタルインボイスの検証
Version 1.3.5 · JPVerify · https://www.jpverify.com
When to use / いつ使うか
- You have a JP PINT 1.1.3 UBL Invoice XML (Japanese Peppol e-invoice / デジタルインボイス) and need to know whether it is valid.
- You are building or testing e-invoice generation and want rule-level errors to fix.
- You received an e-invoice and want schema/rule validity plus the seller's T-number status before accepting it.
Not for PDF or image invoices: JPVerify does not read files. Read the invoice yourself and send its T-number, issuer name and date to /v1/jp/invoices/check-issuer (skill jp-invoice-number-check).
Connect / 接続
JPVerify is a paid, per-call API. Pick the first option that applies; never guess credentials.
- API key (recommended). If the environment has
JPVERIFY_API_KEY(ajpv_live_…key the user created), send it on every call:- HTTP: header
Authorization: Bearer $JPVERIFY_API_KEY(orX-API-Key). - MCP: if the JPVerify Claude Code plugin is installed, the
jpverifyMCP server is already configured and uses the key saved in the plugin's settings (/plugin→ JPVerify → Configure), notJPVERIFY_API_KEY. Otherwise:claude mcp add --transport http jpverify https://api.jpverify.com/mcp --header "Authorization: Bearer $JPVERIFY_API_KEY" --header "X-JPVerify-Client: jp-pint-invoice-validation/1.3.5"Each successful call is deducted from the user's prepaid USD credits; failed or invalid calls are refunded automatically. Before a large batch, check the balance for free:GET https://api.jpverify.com/v1/account/balancewith the same header, or the MCP tooljpverify_balance.
- HTTP: header
- x402 wallet. If you have an x402 client with USDC on Base (
eip155:8453) and the user approved a budget, call without a key: the API answers HTTP 402 with the exact price; sign and retry withPAYMENT-SIGNATURE. Pay only within the approved budget. - Neither. Do not pay and do not invent a key. The MCP server also works without a key for the free tool
jpverify_guide(claude mcp add --transport http jpverify https://api.jpverify.com/mcp); use it to confirm which call fits, then tell the user they can create a free account with starter credit at https://www.jpverify.com/signup?ref=jp-pint-invoice-validation and setJPVERIFY_API_KEY.
Always send X-JPVerify-Client: jp-pint-invoice-validation/1.3.5 on HTTP calls. Never print, log or share the API key.
Workflow / 手順
- Send the complete XML document as the
xmlstring (UTF-8, starting with the XML declaration or<Invoice). Do not pretty-print or edit it; validation is on the exact document. - Set
registry_enhance: trueif you also need the seller's T-number checked in the NTA registry (same price). - If
document_validis false, list the failing rules fromerrors/checks(rule ID, message, location) so the user or developer can fix them, then validate the corrected file once.
Endpoints and prices / エンドポイントと料金
| Endpoint | MCP tool | Price (USD) | Use when | Returns |
|---|---|---|---|---|
POST /v1/jp/invoices/validate-pint | — | $0.02 | You need offline validation of a JP PINT 1.1.3 UBL Invoice before accounting or payment workflow acceptance. | Official document_valid from pinned OASIS UBL 2.1 XSD and OpenPeppol JP PINT 1.1.3 Schematron, plus separate decision/trusted fields and optional NTA registry evidence. |
Request fields / リクエスト項目
| Endpoint | Required fields | Optional fields |
|---|---|---|
POST /v1/jp/invoices/validate-pint | xml | registry_enhance |
Where no field is required, send at least one identifier. JPVerify does not read files: send the fields you read. response_language is ja, en or both (default both).
Japanese descriptions and request examples for every endpoint: references/endpoints.md, references/examples.md.
Reading results / 結果の読み方
document_validis the official result: the document passed the pinned UBL 2.1 XSD and the JP PINT 1.1.3 Schematron (versionshows what was applied).decision(accepted,rejected,manual_review,not_evaluated) andtrustedare a separate workflow signal that also considers registry evidence whenregistry_enhanceis on. A document can be schema-valid but still need review (e.g. the T-number is not registered).warningsare non-fatal rule warnings; report them but do not treat them as failures.- The result is validation evidence only — not legal, tax or Peppol conformance certification.
Errors and spending / エラーと費用
| Response | What to do |
|---|---|
200 | Use the result (see "Reading results"). With an API key, X-JPVerify-Credits-Charged and X-JPVerify-Credits-Remaining show the cost and balance. |
401 invalid_api_key | The key is missing, wrong or revoked. Ask the user to check JPVERIFY_API_KEY; do not retry with guesses. |
402 insufficient_credits (API key) | Stop. Nothing was charged. Tell the user to top up at https://www.jpverify.com/account/billing. Do not retry. |
402 with x402 payment requirements (no key) | Pay only within the approved budget, using the exact amount in the response. |
422 | Invalid input; nothing was charged. Fix the input (the error says which field) and call again once. |
5xx / timeout | Not charged (credits are refunded). Retry once later; then report the failure. |
Spending rules:
- Before a batch call, or any plan that will cost more than $0.50 in total, state the number of calls and the total price and get the user's go-ahead.
- Do not call the same paid endpoint repeatedly for the same input; reuse the result you already have.
- Prices in the endpoint table are per successful call in USD (the same with an API key or x402).
Example / 呼び出し例 (POST /v1/jp/invoices/validate-pint)
API key:
# invoice.xml: your JP PINT 1.1.3 UBL Invoice
jq -n --rawfile xml invoice.xml '{xml: $xml, registry_enhance: true}' |
curl -X POST https://api.jpverify.com/v1/jp/invoices/validate-pint \
-H "Authorization: Bearer $JPVERIFY_API_KEY" \
-H "X-JPVerify-Client: jp-pint-invoice-validation/1.3.5" \
-H "Content-Type: application/json" \
--data-binary @-
import os, pathlib, requests
response = requests.post(
"https://api.jpverify.com/v1/jp/invoices/validate-pint",
headers={"Authorization": f"Bearer {os.environ['JPVERIFY_API_KEY']}",
"X-JPVerify-Client": "jp-pint-invoice-validation/1.3.5"},
json={"xml": pathlib.Path("invoice.xml").read_text(encoding="utf-8"), "registry_enhance": True},
timeout=60,
)
print(response.status_code, response.json())
x402 (no account):
# No key: shows the HTTP 402 x402 price; pay with an x402 client and retry with PAYMENT-SIGNATURE.
jq -n --rawfile xml invoice.xml '{xml: $xml, registry_enhance: true}' |
curl -i -X POST https://api.jpverify.com/v1/jp/invoices/validate-pint \
-H "X-JPVerify-Client: jp-pint-invoice-validation/1.3.5" \
-H "Content-Type: application/json" \
--data-binary @-
Full SDK examples (Python x402, JavaScript @x402/fetch): https://api.jpverify.com/docs/x402
Limits and privacy / 制限とプライバシー
- Results are a public-registry pre-check with the source and as-of date of the data. They are not KYB, AML or sanctions screening, and not legal, tax or accounting advice. A "not found" does not mean the entity does not exist or is risky.
- If
manual_review_requiredis true or a status is ambiguous, show the evidence to the user and let them decide; do not decide on their behalf. - Only send data the user is entitled to process. JPVerify takes fields, not files; do not send personal details (names, phone numbers, e-mail addresses) that a check does not need.
- Docs: API key https://api.jpverify.com/docs/api-key · x402 https://api.jpverify.com/docs/x402 · terms https://api.jpverify.com/en/terms · privacy https://api.jpverify.com/en/privacy
- Downloads
- 438All time
- Security audit
- Review
- Last updated
- 4d ago
- Current version
- v1.3.5
- License
- MIT-0
