Invoices Counterparty Check
by api.jpverify.com in Markets & finance
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は名称検索に使わず、元データは再販しません。
https://api.jpverify.com/v1/invoices/counterparty-check- Price
- $0.05
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 854 ms
- 936 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
How to call it
POST https://api.jpverify.com/v1/invoices/counterparty-check
Each call costs $0.05 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://api.jpverify.com/v1/invoices/counterparty-check
content-type: application/json
{
"participant_id": "iso6523-actorid-upis::0088:123456789",
"response_language": "both",
"vat_id": "DE123456789"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
country_code | string | No | |
name | string | No | |
participant_id | string | No | Qualified Peppol participant identifier in scheme::value form; known legacy ISO 6523 scheme:value is normalized server-side. |
response_language | string | No | Response presentation language: ja, en, or both. / レスポンス表示言語: ja(日本語)、en(英語)、both(両方)。 One of: ja, en, both. Default: "both". |
vat_id | string | No | Known EU VAT ID; VIES does not support name search. |
Example response
The provider's example. We can't check it without paying.
{
"checks": [],
"conflicts": [],
"decision": "verified",
"entity_match": {
"status": "not_requested"
},
"peppol": {
"status": "discoverable"
},
"vat": {
"status": "valid"
}
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.05.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.jpverify.com/v1/invoices/counterparty-check' \
-H 'content-type: application/json' \
--data-raw '{"participant_id":"iso6523-actorid-upis::0088:123456789","response_language":"both","vat_id":"DE123456789"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://api.jpverify.com/v1/invoices/counterparty-check' \
-H 'content-type: application/json' \
--data-raw '{"participant_id":"iso6523-actorid-upis::0088:123456789","response_language":"both","vat_id":"DE123456789"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.jpverify.com%2Fv1%2Finvoices%2Fcounterparty-check&method=POST
const res = await pay("https://api.jpverify.com/v1/invoices/counterparty-check", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"participant_id": "iso6523-actorid-upis::0088:123456789",
"response_language": "both",
"vat_id": "DE123456789"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.jpverify.com/v1/invoices/counterparty-check",
json={
"participant_id": "iso6523-actorid-upis::0088:123456789",
"response_language": "both",
"vat_id": "DE123456789",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 880 ms | $0.05 |
| 6 h ago | Passed | 402 | 920 ms | $0.05 |
| 10 h ago | Passed | 402 | 839 ms | $0.05 |
| 14 h ago | Passed | 402 | 842 ms | $0.05 |
| 18 h ago | Passed | 402 | 886 ms | $0.05 |
Show 10 older checks
| 22 h ago | Passed | 402 | 834 ms | $0.05 |
| 26 h ago | Passed | 402 | 845 ms | $0.05 |
| 30 h ago | Passed | 402 | 817 ms | $0.05 |
| 33 h ago | Passed | 402 | 883 ms | $0.05 |
| 37 h ago | Passed | 402 | 893 ms | $0.05 |
| 41 h ago | Passed | 402 | 851 ms | $0.05 |
| 44 h ago | Passed | 402 | 881 ms | $0.05 |
| 2 days ago | Passed | 402 | 465 ms | $0.05 |
| 2 days ago | Passed | 402 | 843 ms | $0.05 |
| 2 days ago | Passed | 402 | 869 ms | $0.05 |