Japan Invoice Batch Verify
Batch Japanese qualified-invoice verification / 適格請求書登録番号一括検証: verify up to 10 T+13 digit invoice registration numbers against Japan's NTA registry for accounting and AP workflows. / 最大10件のT+13桁インボイス登録番号を国税庁データと照合し、会計・買掛金処理に利用できます。
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.05 USDC on Base to 0xe4A4…0572F. The signed payment is good for 5 minutes.
- Paid to
- 0xe4A4…0572F
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 50000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xe4A4E5B226bE71e7b6eD523bc7a91089c770572F",
"amount": "50000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"response_language": "both",
"registration_numbers": [
"T1013301046627"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"count": 1,
"results": [
{
"match": true,
"status": "registered"
}
]
}
}
},
"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",
"required": [
"registration_numbers"
],
"properties": {
"response_language": {
"enum": [
"ja",
"en",
"both"
],
"type": "string",
"default": "both",
"description": "Response presentation language: ja, en, or both. / レスポンス表示言語: ja(日本語)、en(英語)、both(両方)。"
},
"registration_numbers": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 10,
"minItems": 1
}
}
},
"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": {
"type": "object",
"count": {
"type": "integer"
},
"results": {
"type": "array",
"items": {
"type": "object"
}
},
"max_batch_size": {
"type": "integer"
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-08-16 23:54Z
- Last indexed by Roundhouse
- 2026-09-15 23:40Z
- Last enriched (probe, favicon, geo)
- 2026-09-23 20:45Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 405
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 22 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Japan Invoice Batch Verify and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Japan%20Invoice%20Batch%20Verify' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.jpverify.com/jp-invoice/verify-batch, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.