/authorities
The top passages on a topic ranked by graph centrality, so an agent can triage a field before reading into it.
Relevance ranking answers "what matches?". Centrality answers "what does this field consider load-bearing?". They are different questions, and for an agent entering an unfamiliar domain the second one is usually the useful one.
Authorities returns the well-connected passages for a topic or entity, which is how you fill a context window with the sources a domain expert would have started from rather than the ones that happened to match the query string.
Request
curl -H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/authorities?topic=technology&limit=10"| Parameter | Type | Description |
|---|---|---|
topicrequired | string | A topic tag or entity name. |
limit | integer default: 10 | Number of passages. |
Response
The same WebHit[] shape as /search, ordered by centrality.
From an agent
This endpoint is also exposed as the MCP tool authorities, so an agent can call it without any HTTP code.
// What are the authoritative sources on this topic?
{ "topic": "science", "limit": 10 }Try this endpoint
Every endpoint is available on the free tier. Get a key and run the example above unchanged.