Browse documentation
Who is central on this topic
Coverage Graph: the top passages about a topic (or entity), ranked by graph centrality rather than by match to a query.
get
/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.
Parameters
| Name | Type | Description |
|---|---|---|
topicrequired | string | Topic tag, or an entity / salient term. |
limit | integer | Maximum hits, default 10. |
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, or past a hard-capped monthly quota. `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 is a tool with these parameter names unchanged. See Errors for what to do with each status.