Entity Resolver API: Any entity name in; Wikidata id, labels, aliases and the external — SEC, LEI and Wikidata identifiers
Any entity name in; Wikidata id, labels, aliases and the external identifiers other datasets key on (SEC CIK, LEI, ticker, NAICS) out, with endpoint URLs where they map. Turns name matching into a key join. Free, no key.
Free — no key, no signup, rate-limited to 60 calls per minute per client.
How do you call it?
GET /v1/entity/resolve — product id
entity_resolve. Over MCP, call answerpool_get with
product_id=entity_resolve.
curl "https://answerpool.io/v1/entity/resolve?q=Nvidia"
Live call: https://answerpool.io/v1/entity/resolve?q=Nvidia · JSON sample: /v1/samples/entity_resolve
What does the answer look like?
A representative response, the same static sample served at /v1/samples/entity_resolve.
as_of | 2026-09-03T17:00:00Z |
|---|---|
query | Nvidia |
qid | Q182477 |
label | Nvidia |
description | American multinational technology company |
aliases | NVIDIA Corporation |
instance_of | public company |
industry | semiconductor industry |
country | United States of America |
headquarters | Santa Clara |
other_candidates | (empty) |
note | One lookup, the identifiers several domains key on. When an SEC CIK is present, the crosswalk into our SEC endpoints is a key join rather than a name match. |
source | Wikidata (CC0) |
refresh_after | 2026-09-18T00:00:00.000Z |
external_ids
| key | label | value | our_endpoint |
|---|---|---|---|
| sec_cik | SEC Central Index Key | 0001045810 | /v1/sec/entity?cik=0001045810 |
| lei | Legal Entity Identifier | 549300S4KLFTLO7GSQ80 | — |
The same sample as raw JSON
{
"as_of": "2026-09-03T17:00:00Z",
"query": "Nvidia",
"qid": "Q182477",
"label": "Nvidia",
"description": "American multinational technology company",
"aliases": [
"NVIDIA Corporation"
],
"instance_of": [
"public company"
],
"industry": [
"semiconductor industry"
],
"country": [
"United States of America"
],
"headquarters": [
"Santa Clara"
],
"external_ids": [
{
"key": "sec_cik",
"label": "SEC Central Index Key",
"value": "0001045810",
"our_endpoint": "/v1/sec/entity?cik=0001045810"
},
{
"key": "lei",
"label": "Legal Entity Identifier",
"value": "549300S4KLFTLO7GSQ80",
"our_endpoint": null
}
],
"other_candidates": [],
"note": "One lookup, the identifiers several domains key on. When an SEC CIK is present, the crosswalk into our SEC endpoints is a key join rather than a name match.",
"source": "Wikidata (CC0)",
"refresh_after": "2026-09-18T00:00:00.000Z"
}How fresh is it, and where does the data come from?
The fastest source behind this answer can change daily, so every response carries a refresh_after timestamp — right now it would be 2026-09-18T00:00:00.000Z. Schedule the next call on that value rather than on a guess.
- Wikidata (CC0) — upstream:
https://www.wikidata.org/w
Method version 0.1.0 ·
serving cache 7 days ·
every response carries a result_id you can resolve at
/v1/provenance.
When should you use it?
You have a name and need identifiers that work in other systems.
What you skip building
- hand-built identifier mappings
- name-matching false positives
- SPARQL
When should you not use it?
SEC-only resolution (/v1/sec/resolve is authoritative for CIK) or federal award recipients (/v1/funding/recipients).
Where else can you find this?
- Catalog entry (JSON, free)
- OpenAPI schema — input and output types, prices, the 402 flow
- llms.txt — every product in one plain-text document