Fact Lookup — Look up facts about anything

Tools / Fact Lookup

Search Entities

Search Wikidata entities by keyword. Returns matching entities with IDs, labels, descriptions, and links to Wikipedia and Wikidata.

Returns: List of matching Wikidata entities with ID, label, description, and URLs

Parameters

query *stringSearch term — person, place, organization, concept, etc.

languagestringLanguage code for labels and search (default "en")

limitnumberMax results to return (1-20)

Example

Search for Tesla

curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
  -d '{
  "tool": "fact-lookup",
  "skill": "search",
  "input": {
    "query": "Tesla"
  }
}' \
  https://api.toolrouter.com/v1/tools/call

Get Entity Facts

Get comprehensive structured facts about any entity. Accepts a name or Wikidata Q-ID. Returns up to 60 properties with values resolved to human-readable labels — population, founding date, coordinates, CEO, awards, and more.

Returns: Structured entity data with label, description, aliases, Wikipedia URL, and key facts resolved to readable values

Parameters

entity *stringEntity name (e.g. "Tokyo", "Albert Einstein", "Apple Inc") or Wikidata Q-ID (e.g. "Q1490")

languagestringLanguage for labels (default "en")

Example

Get facts about Tokyo

curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
  -d '{
  "tool": "fact-lookup",
  "skill": "get_entity",
  "input": {
    "entity": "Tokyo"
  }
}' \
  https://api.toolrouter.com/v1/tools/call

SPARQL Query

Run a SPARQL query against Wikidata for complex multi-entity questions. Supports filtering, sorting, aggregation, and relationship traversal across 100M+ entities.

Returns: SPARQL query results as an array of row objects with column names as keys

Parameters

sparql *stringSPARQL query string. Must include SERVICE wikibase:label for readable results. LIMIT is auto-added if missing (max 500).

Example

Top 10 most populous countries

curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
  -d '{
  "tool": "fact-lookup",
  "skill": "sparql_query",
  "input": {
    "sparql": "SELECT ?country ?countryLabel ?population WHERE { ?country wdt:P31 wd:Q6256 . ?country wdt:P1082 ?population . SERVICE wikibase:label { bd:serviceParam wikibase:language \"en\". } } ORDER BY DESC(?population) LIMIT 10"
  }
}' \
  https://api.toolrouter.com/v1/tools/call

Quick Start

MCP (Claude Code)

claude mcp add --transport stdio \
  --env TOOLROUTER_API_KEY=YOUR_API_KEY \
  toolrouter -- npx -y toolrouter-mcp

REST API

curl -H "Authorization: Bearer $TOOLROUTER_API_KEY" \
  -d '{"tool":"fact-lookup","skill":"search","input":{}}' \
  https://api.toolrouter.com/v1/tools/call

Frequently Asked Questions

Do I search first, or can I ask directly for a fact?

Either works. `get_entity` accepts a plain name or Q-ID for common entities, while `search` helps you find the right entity first.

What kinds of facts come back?

`get_entity` returns up to 60 structured facts such as population, founding date, coordinates, website, CEO, and country.

When should I use SPARQL instead of `get_entity`?

Use `sparql_query` when you need lists, rankings, comparisons, or other multi-entity answers.

How do I keep the query reliable?

Start with `search` or `get_entity`, and include a label service plus `LIMIT` in SPARQL so the result stays readable.