Knowledge your AI agent can actually afford to read.

Fetching an encyclopedia page costs an agent roughly 15,000 tokens of HTML to recover about 500 tokens of facts. Wikexa returns the facts — structured JSON, pre-processed once, served from the edge. No key, no account.

4 tools
lookup, article, search, recent
5–12 ms
warm response at the edge
~30×
fewer tokens than fetching the page
Free
for individuals and open projects
How it works

One call. Structured facts. Done.

Reference sites have APIs, but they were built to render pages — they return markup, navigation chrome and citation scaffolding. An agent pays for all of it in tokens and discards nearly all of it. Wikexa does that parsing once, ahead of time, and stores the answer.

1

Ask by name

Send whatever the user said. Apple, Apple Inc and Q312 all resolve to one entity through redirects and our alias index.

2

Get only the facts

Infobox as key–value pairs, a ~200-token summary, categories, related entities, and normalised claims. No markup, no empty fields.

3

Pull more if you need it

article() returns sections as a JSON array and accepts sections and max_chars, so a long page never floods your context.

# Ask GET /v1/lookup?entity=Tim%20Cook # Facts come back { "title": "Tim Cook", "wikidata_id": "Q265852", "description": "American business executive", "summary": "Timothy Donald Cook is an…", "facts": { "employer": "Apple Inc.", "occupation": "business executive" }, "source_url": "https://en.wikipedia.org/…", "license": "CC BY-SA 4.0" }
The tools

Four calls cover almost everything.

Every tool is available over MCP and as a plain REST endpoint. Both surfaces run the same handler, so they cannot drift apart.

lookup(entity)

Facts and a short summary

Structured facts plus a ~200-token summary. Resolves aliases, redirects and entity IDs, so you can pass whatever the user typed.

article(title, sections?, max_chars?)

The whole page, structured

Sections as a JSON array with the infobox parsed out. Ask for one section by name, or cap the payload — the token dial is yours.

search(query, limit?)

When you don't know the title

Full-text relevance blended with monthly pageviews, so apple returns Apple Inc. and the fruit — not a disambiguation stub.

recent(topic?, hours?)

Newer than your training cutoff

Articles changed in the last hours or days — elections, appointments, releases, deaths. The freshness a static model cannot have.

Why it's fast

Pre-processed once, served from the edge.

The expensive work — parsing, resolving, structuring — is done ahead of time, not while your agent waits. What is left at request time is a lookup and a response, served from close to the caller.

Single-digit milliseconds

Warm lookups typically return in under 15ms wherever they are called from. No cold start to sit through, no query to plan, no rate-limit dance before you get an answer.

Free where it should be

Individuals, research and open-source projects use it at no cost. Businesses running it at volume take a service plan that funds the infrastructure.

Built to be found by software.

MCP over streamable HTTP, an OpenAPI description, llms.txt, and the usual well-known discovery documents. Listed in the Model Context Protocol registry as com.wikexa/knowledge.

MCPJSON-RPC 2.0OpenAPI 3.1llms.txtREST
Integration guide
Try it

Nothing to sign up for.

curl -s 'https://wikexa.com/v1/lookup?entity=Ada%20Lovelace'

curl -s -X POST https://wikexa.com/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"lookup","arguments":{"entity":"Ada Lovelace"}}}'

Or point any MCP client at https://wikexa.com/mcp.