Browse documentation
Who is central on this topic — GET /authorities
Coverage Graph: the top passages about a topic (or entity), ranked by graph centrality rather than by match to a query.
/authorities Request
curl \
-H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/authorities?topic=<topic>" Behaviour
Trust-triage a field you do not know yet — read the central sources first instead of reading junk into your context and discovering later that it was junk.
Costs 2 credits; a call that runs and fails costs 1.
Parameters
| Name | Type | Description |
|---|---|---|
topicrequired | string | Topic tag, or an entity / salient term. |
limit | integer | Maximum hits, default 10, maximum 100 (a larger value is clamped; `total` still reports the real match count). |
Responses
| Status | Meaning |
|---|---|
200 | Top passages by graph centrality. |
401 | Missing, unknown or revoked key. A key minted moments ago can answer 401 until it propagates to the serving fleet. |
429 | Over the per-minute rate (spent in credits), or a hard-capped key without the credits this call costs. `retry-after` is present on the rate-limit case only. |
Response body
WebSearchResponse
| Name | Type | Description |
|---|---|---|
facets | object | Present only when facets=true |
moderequired | "keyword" | "semantic" | "hybrid" | The mode actually used |
partial | boolean | true when at least one shard failed or timed out — the answer is short because a slice of the corpus was unreachable, NOT because that is all there is. Never treat a partial result as complete. |
resultsrequired | object[] | — |
routedrequired | boolean | true when the router chose the vertical, false when you named it |
totalrequired | integer | — |
vertical | string | null | The vertical actually queried |
The same call over MCP
This capability is authorities on the
MCP server, taking the same parameters and returning the same body. A parity test
in the API fails the build if the two ever diverge, so you can read either
reference and use the other.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "authorities",
"arguments": {
"topic": "<topic>"
}
}
} Most clients build that frame for you — see Connect a client.
See Errors for what to do with each status, and Retries and backoff for which are worth repeating.
FAQ
- What does 200 mean on GET /authorities?
- Top passages by graph centrality.
- What does 401 mean on GET /authorities?
- Missing, unknown or revoked key. A key minted moments ago can answer 401 until it propagates to the serving fleet.
- What does 429 mean on GET /authorities?
- Over the per-minute rate (spent in credits), or a hard-capped key without the credits this call costs. `retry-after` is present on the rate-limit case only.