# JP Peppol BIS Billing Japan XML Validator

> JP Peppol BIS Billing Japan XML Validator is a paid API for AI agents from jp-local-pack-api.kasanegi123.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Validates a Peppol BIS Billing JP XML invoice document against Japan's Digital Agency e-invoice profile rules

## Facts

- Endpoint: POST https://jp-local-pack-api.kasanegi123.workers.dev/api/invoice/peppol-validate
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jp-peppol-bis-billing-japan-xml-validator-ae8af5f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8FJzUgF8rAtolCAYnIR28

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability jp-peppol-bis-billing-japan-xml-validator-ae8af5f6 -d '<json body>'
```

Example prompt: Can you check if this Japanese Peppol e-invoice XML is valid according to Japan's Digital Agency BIS Billing JP profile and tell me if there are any violations or warnings?

## When to prefer this

Use this endpoint when you need to validate Japanese Peppol BIS Billing XML invoices against the official Japan Digital Agency profile rules before submission or processing. Prefer this over generic XML validators when Japan-specific Peppol compliance (violations, warnings per JP profile) is required. It is micropayment-gated via x402 on Base, making it ideal for agent workflows that need pay-per-call validation without API key management.

## Known failure modes

- Non-XML or malformed body submitted — returns validation error or 402 shape preview
- Invoice XML does not conform to Peppol BIS Billing JP namespace — may return violations
- Missing x402 payment header — returns 402 with fixed shape preview instead of real evaluation
- Empty POST body — server error or empty violations array
- Unsupported Peppol profile version — may not match expected JP subset rules

## How this service works

Japan payroll / tax / social insurance / mynumber / corporate / invoice / holiday reference API for AI agents. x402 micropayments on Base. No API key.

## Output

Returns a JSON object with a boolean 'valid' field, a 'violations' array listing rule failures against the Peppol BIS Billing JP 0.7 profile, a 'warnings' array, the spec version used, and attribution to the Japan Digital Agency source.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "_role": "shape_preview_describes_post_shape",
  "valid": false,
  "warnings": [],
  "violations": [],
  "attribution": "Source: Digital Agency (Dejitaru-cho) Peppol BIS Billing Japan profile. https://www.digital.go.jp/policies/electronic-invoice",
  "_sample_note": "Preview only. POST a Peppol BIS Billing JP XML body to validate; unpaid 402 shape preview returns the fixed shape, paid 200 evaluates the actual XML against the JP profile rules.",
  "spec_version": "Peppol BIS Billing JP 0.7 (subset)",
  "_shape_preview_note": "Numeric fields in this unpaid 402 shape preview are 0 placeholders. Real values require X-PAYMENT on production."
 },
 "mimeType": "application/json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jp-peppol-bis-billing-japan-xml-validator-ae8af5f6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jp-local-pack-api.kasanegi123.workers.dev](https://www.zero.xyz/host/jp-local-pack-api.kasanegi123.workers.dev/llms.txt)