# Strale EORI Number Validator

> Strale EORI Number Validator is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054/call, status unknown (last checked 2026-09-14).

Validates an Economic Operators Registration and Identification (EORI) number for customs and trade compliance, returning a structured result with an audit trail.

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/eori-validate
- Price: $0.054/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-eori-number-validator-070e322c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wgpLJH-0EYjBQIZMmHx95

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 strale-eori-number-validator-070e322c
```

Example prompt: Can you check whether the EORI number DE123456789012345 is valid and registered for customs trading?

## When to prefer this

Choose this endpoint when you need auditable, independently-tested EORI validation with a cryptographic audit trail — particularly for compliance workflows, agent-driven trade automation, or when operating across multiple EU/UK countries. Prefer this over DIY scraping of the EU EORI registry when you need structured JSON output, reliability, and a tamper-evident audit record.

## Known failure modes

- Invalid EORI format returns a validation error
- EORI number not found in the registry returns a not-found or invalid status
- Malformed query parameter causes a 400 Bad Request
- Upstream customs registry unavailability may cause timeouts or 503 errors
- Payment failure via x402 protocol results in 402 Payment Required

## How this service works

The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.

## Output

Returns a structured JSON object indicating whether the provided EORI number is valid and registered, along with associated entity details where available. Every response includes an audit record with a cryptographic chain hash for traceability and compliance purposes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "eori"
     ],
     "properties": {
      "eori": {
       "type": "string",
       "description": "EORI number (e.g. DE123456789012345)"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-eori-number-validator-070e322c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)