# JPVerify Cross-Border Entity Resolution (JP/GB)

> JPVerify Cross-Border Entity Resolution (JP/GB) is a paid API for AI agents from api.jpverify.com, paid per call via x402, $0.04/call, status unknown (last checked 2026-09-15).

Resolves and verifies Japanese or UK company identities using official sources (NTA/gBizINFO for Japan, Companies House for UK), returning a projected verification result without exposing raw upstream data.

## Facts

- Endpoint: POST https://api.jpverify.com/v1/entities/resolve-cross-border
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jpverify-cross-border-entity-resolution-jp-gb-9999e93a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_skNu6mUOO_NHMciDg1FGN

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 jpverify-cross-border-entity-resolution-jp-gb-9999e93a -d '<json body>'
```

Example prompt: Can you verify that 'Mitsubishi Corporation' with corporate number 1080001000209 is a legitimately registered entity in Japan using official NTA sources, and flag any identity conflicts?

## When to prefer this

Use this endpoint when you need official, evidence-backed identity verification for a Japanese or UK company specifically — especially in KYB, AML, or due diligence workflows where raw upstream data is not required and a clean projected verdict is sufficient. Prefer this over generic company lookup endpoints when the jurisdiction is JP or GB and you need hard conflict detection. Not suitable for jurisdictions outside Japan and the UK, or when raw registry data is required.

## Known failure modes

- Entity not found in official registry — returns unverified status with no match
- Hard identity conflict detected (name/number mismatch) — returns conflict flag, never verified
- Invalid or malformed corporate/Companies House number — returns validation error
- Unsupported jurisdiction provided (neither JP nor GB) — returns parameter error
- Upstream registry temporarily unavailable — may return service error or degraded response
- Ambiguous entity with multiple possible matches — returns conflict or unverified status

## Output

Returns a projected verification result indicating whether the entity's identity is verified, unverified, or conflicted, including the resolved official name, registration number, jurisdiction (JP or GB), and any detected identity conflicts. Raw upstream NTA, gBizINFO, or Companies House response data is never exposed. Hard identity conflicts (e.g. mismatched name vs. number) will not be returned as verified.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jpverify-cross-border-entity-resolution-jp-gb-9999e93a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.jpverify.com](https://www.zero.xyz/host/api.jpverify.com/llms.txt)