Search built for agents, not for reading
unlob returns passages, not links. The index is admission-controlled rather than exhaustive, so what comes back is short enough to put straight into a context window — and every hit carries the trust and corroboration signals you would otherwise have to infer.
REST
21 endpoints
One GET per question. Generated from the API's own description.
MCP
11 tools
The same capabilities, the same parameters, over Streamable HTTP or stdio.
Beyond search
A graph
Corroborate a claim, brief yourself on an entity, or get a packed context set.
Four things worth knowing first
Authentication
One key, two header spellings, and the minute after you mint it.
Search modes
Keyword, semantic, hybrid — and the query grammar.
Filters and sorting
Every filter, what it narrows, and which ones only bias.
Reading a result
What a hit carries, and the one field that changes what it means.
Still deciding?
These pages assume you have chosen unlob and want to use it. The case for choosing it is on the main site: the 2026 landscape maps every web search API with sourced pricing, the comparisons each name where the competitor wins, and why an own index matters covers what you inherit when a search API resells someone else's results.
For agents
Everything on this site is also readable by machine, without a key: llms.txt, openapi.json, mcp/tools.json, and describe, which reports what this deployment can do right now rather than what the docs said last month.