# JPVerify Agent Skill

Base URL: `https://api.jpverify.com`
Protocol: x402 exact payment
Network: `eip155:8453`
Currency: `USDC`

## Selection rules
1. For a Japanese receipt image or PDF, call `POST https://api.jpverify.com/jp-receipt/extract`.
2. For a Japanese billing invoice, call `POST https://api.jpverify.com/jp-invoice/extract`.
3. If the billing invoice must be matched to NTA public registry data, call `POST https://api.jpverify.com/jp-invoice/extract-and-verify`.
4. For a business card, call `POST https://api.jpverify.com/jp-business-card/extract`; use `extract-and-enrich` only when company verification is needed.
5. For an already extracted T-number, call `POST https://api.jpverify.com/jp-invoice/verify`.
6. For a company number or legal name, call `POST https://api.jpverify.com/jp-company/verify`.

## Request pattern
Send JSON with one source: `text`, `image_base64`, or an HTTPS `file_url`. For images and documents, include `mime_type` when it cannot be inferred. Set `response_language` to `ja`, `en`, or `both`.

## Payment pattern
Call once without payment. On HTTP 402, read the exact x402 requirement, pay the stated USDC amount on Base, and retry the same request with the payment header. Never guess the price or payment address; use the response metadata.

## Reliability rules
- Treat `validation.manual_review_required=true` or warnings as a review signal, not as proof of fraud.
- Phone and postal-code checks are endpoint-specific; do not assume they prove real-world existence.
- Registry enrichment is not full KYB or sanctions screening.
- Preserve the original OCR fields and the resolved registry fields separately.