# eudata402 Entity/Company Resolution with Wikidata Cross-linked Identifiers

> eudata402 Entity/Company Resolution with Wikidata Cross-linked Identifiers is a paid API for AI agents from x402-seller-202595743428.europe-west1.run.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Resolves a company or entity name to structured identifiers including LEI, ISIN, ticker, website, country, and inception date via Wikidata cross-linking.

## Facts

- Endpoint: GET https://x402-seller-202595743428.europe-west1.run.app/entity
- 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/eudata402-entity-company-resolution-with-wikidata-cross-linked-00723f83
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-zMOfTeLQArFrzPDfypyN

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 eudata402-entity-company-resolution-with-wikidata-cross-linked-00723f83
```

Example prompt: Can you look up Volkswagen AG and give me its LEI, ISIN, ticker symbol, country, and founding year?

## When to prefer this

Choose this endpoint when you need to resolve a company name to structured cross-linked financial identifiers (LEI, ISIN, ticker) in a single call using Wikidata as the authoritative source. Prefer it over dedicated LEI-only or ISIN-only lookups when you need multiple identifier types simultaneously. It is especially useful for entity enrichment pipelines, compliance onboarding, and financial research workflows where a human-readable name is the only starting point.

## Known failure modes

- Ambiguous company name matching multiple entities — returns best guess or top match
- Entity exists in Wikidata but lacks financial identifiers (LEI/ISIN may be null)
- Unknown or very small company not present in Wikidata — returns empty or no match
- Query string too vague (e.g. just 'Bank') yields irrelevant entity
- Rate limiting or upstream Wikidata API unavailability causing timeout or 402 payment required re-prompt

## How this service works

Entity/company resolution with cross-linked identifiers (Wikidata). POST {query}. Returns {id, label, description, identifiers: {lei, isin, ticker, website, country, inception}}.

## Output

Returns a JSON object with fields: id (Wikidata entity ID), label (canonical name), description (short Wikidata description), and an identifiers object containing LEI, ISIN, ticker, website, country, and inception date where available.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "Company or entity name"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/eudata402-entity-company-resolution-with-wikidata-cross-linked-00723f83/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-seller-202595743428.europe-west1.run.app](https://www.zero.xyz/host/x402-seller-202595743428.europe-west1.run.app/llms.txt)