Resolve raw entity strings — names, URLs, partial mentions — to a stable canonical Entidex ID. Use this before any other endpoint when your input data is messy.
The simplest case: one input, one canonical ID. Returns the canonical entity when the match is confident, or an ENTITY_NOT_RESOLVED error carrying the surfaced candidate matches and their scores when the input is ambiguous. Accepts either q or query. For lists, use batch reconciliation below — it returns a confidence band per input.
curl -s "https://entidex.com/api/v1/entities/resolve?q=Anthropic" \
-H "Authorization: Bearer $ENTIDEX_API_KEY"For lists of 25 or more, post the inputs as a single batch. Each input returns its own confidence band; apply a threshold (we recommend ≥ 0.75 for autopilot) and queue the rest for review.
curl -s -X POST "https://entidex.com/api/v1/entities/resolve/batch" \
-H "Authorization: Bearer $ENTIDEX_API_KEY" \
-H "Content-Type: application/json" \
-d '{"inputs":["Anthropic","OpenAI","Mistral AI"]}'Each batch result carries a confidence (0–1) and a band. resolved is true for the auto and strong bands.
Create a free account to get an API key (1,000 monthly credits, 1,500 with a verified email + phone), then resolve, read and ground in minutes. Or try the keyless scan first.