# Denpyo — Japan Invoice & Receipt Reader API (x402)

Turn Japanese invoices (請求書) and receipts (領収書) into normalized JSON and verify the
qualified-invoice registration number (インボイス登録番号, T + 13 digits) against the National
Tax Agency registry — in one paid call. USDC via x402 on Base & Solana. No API keys.

## Endpoints
- POST https://denpyo-api.hp-vladic.workers.dev/read/invoice  ($0.04)  body: {"url": "..."} or {"base64": "..."}
  → vendor, customer, dates, line items, 8%/10% tax breakdown, registration number,
    NTA verification (active/cancelled, registered name match, corporate record). First 2 pages.
- POST https://denpyo-api.hp-vladic.workers.dev/read/receipt  ($0.03)  body: {"url": "..."} or {"base64": "..."}
  → merchant, date/time, items, totals, tax breakdown, registration number + NTA verification. First page.
- GET  https://denpyo-api.hp-vladic.workers.dev/verify?number=T1180301018771&name=トヨタ自動車  ($0.01)
  → registry-only verification, no OCR.
- GET  https://denpyo-api.hp-vladic.workers.dev/catalog  (free) machine-readable catalog.

## Why
Japanese input-tax credit (仕入税額控除) requires the counterparty to be a registered
qualified-invoice issuer. Denpyo answers "can I book this document?" in one call:
OCR → structured fields → registry verdict (qualified / cancelled / not_registered / no_registration_number).

Errors (invalid document, unreadable file) return 4xx and are NOT charged.
Data: National Tax Agency (国税庁) qualified-invoice-issuer & corporate-number registries, refreshed monthly.
Sister service: Kaisha — Japan Company Registry API (https://kaisha-api.hp-vladic.workers.dev).
Contact: hp.vladic@gmail.com