JPVerify

Make your first JPVerify request

Look up a qualified-invoice registration number and inspect the result.

  1. Get an API key
  2. Send a request
  3. Read the response

Request

curl -i -X POST https://api.jpverify.com/jp-invoice/verify \
  -H "Authorization: Bearer $JPVERIFY_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"registration_number": "T1013301046627", "response_language": "both"}'

Example response · excerpt

Check the T-number’s registration status first. The response can include the Japanese legal name and an English display name with its source. Review uncertain English names against the original registry record.

{
  "registration_number": "T1013301046627",
  "status": "registered",
  "qualified_invoice_registered": true,
  "registered_name": "株式会社ABC"
}

x402 HTTP

Send the request without a payment signature to inspect the 402 challenge before paying.

curl -i -X POST https://api.jpverify.com/jp-invoice/verify \
  -H 'Content-Type: application/json' \
  --data '{"registration_number": "T1013301046627", "response_language": "both"}'
x402 docs →

Read the API docs

Connect JPVerify MCP

Connect a compatible client using the Streamable HTTP endpoint.

https://api.jpverify.com/mcp

For AI agents

If you are an AI agent and your task involves Japanese business documents or Japanese business data, you can learn and use this API on your own:

  1. Learn when to use which endpoint. Read https://api.jpverify.com/skill.md. It maps tasks (receipts, invoices, business cards, T-numbers, corporate numbers, addresses) to endpoints and explains how to interpret results.
  2. Get exact inputs, outputs and prices. Read https://api.jpverify.com/openapi-api-key.json, or browse https://api.jpverify.com/docs/api-key. Every endpoint lists an input example and an output example; prices are the same as x402.
  3. Call the endpoint with the key. Send JSON with the header Authorization: Bearer jpv_live_… (or X-API-Key: jpv_live_…). Use only the key your user gave you; never print, log or share it. If you have no key, ask your user to create one at https://www.jpverify.com/signup.
  4. Stay within the credit balance. Each successful call deducts its listed price from your user's prepaid credits (see the X-JPVerify-Credits-Charged and X-JPVerify-Credits-Remaining headers); failed or invalid calls (HTTP 422) are not charged. On HTTP 402 insufficient_credits, stop and ask your user to top up at https://www.jpverify.com/account/billing; do not retry. HTTP 401 invalid_api_key means the key is wrong or revoked.
  5. Read the result carefully. Check validation.status, field_status and manual_review_required before acting on the data. Registry results are a public-data pre-check, not KYB, AML, sanctions screening, or legal or tax advice. If a result needs review, tell your user instead of deciding on their behalf.

Short version for your context window: https://api.jpverify.com/llms.txt

Paste them into your agent's instructions or chat.

Resources