# LT Company Registry – x402 Payment Settlement Status Probe

> LT Company Registry – x402 Payment Settlement Status Probe is a paid API for AI agents from jar-resolve-305248849433.europe-west1.run.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Confirms whether an x402 micropayment has settled for the Lithuanian company registry service, returning payment status and network details.

## Facts

- Endpoint: GET https://jar-resolve-305248849433.europe-west1.run.app/v1/status
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/lt-company-registry-x402-payment-settlement-status-probe-c2bf3ad3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rtWw76hbAiUR9MqfzCIAg

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 lt-company-registry-x402-payment-settlement-status-probe-c2bf3ad3
```

Example prompt: Check whether the x402 payment for the Lithuanian company registry service has settled — I want to confirm the 0.001 USDC was received before I proceed with the JAR lookup.

## When to prefer this

Use this endpoint when you need to confirm that an x402 micropayment for the Lithuanian company registry (JAR) service has been received before proceeding with a legal entity lookup. It is the correct pre-flight check in any x402-gated workflow targeting this specific registry, not a general payment processor or product catalog.

## Known failure modes

- Payment not yet settled: ok=false with no paid object returned
- Service unreachable: HTTP 5xx or network timeout from the Cloud Run instance
- Unsettled or invalid payment reference: response may indicate payment pending or unrecognized
- Network mismatch: payment on wrong chain (not eip155:84532) may not be recognized

## How this service works

Anonymous x402 seller for official Lithuanian legal-entity lookup (JAR / company registry).

## Output

Returns a JSON object with an 'ok' boolean, a 'paid' object containing asset (USDC), payTo address, price ($0.001), and scheme (exact), a human-readable message ('402x online'), the network identifier (eip155:84532), and a timestamp of the check.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "paid": {
   "asset": "USDC",
   "payTo": "0x0000000000000000000000000000000000000001",
   "price": "$0.001",
   "scheme": "exact"
  },
  "message": "402x online",
  "network": "eip155:84532",
  "timestamp": "2026-08-21T19:22:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/lt-company-registry-x402-payment-settlement-status-probe-c2bf3ad3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jar-resolve-305248849433.europe-west1.run.app](https://www.zero.xyz/host/jar-resolve-305248849433.europe-west1.run.app/llms.txt)