unlob Docs
Browse documentation

Follow the thread

Coverage Graph: the connected neighbourhood of a passage — 'follow the thread'.

get /related

Request

curl \
  -H "x-api-key: $UNLOB_API_KEY" \
  "https://api.unlob.com/related?id=<id>"

Behaviour

A bounded k-hop walk over hosted-on / same-story / topic / entity edges, returning the passages it reaches. The edges are what to read next, so one call decomposes a question that would otherwise be a search per hop.

Raise hops to widen the net; 2 is usually right, and 3 gets noisy fast.

Parameters

NameTypeDescription
idrequiredstringStart passage id.
hopsintegerWalk depth, default 2.
limitintegerMaximum hits, default 10.

Responses

StatusMeaning
200The connected neighbourhood.
401Missing, unknown or revoked key. A key minted moments ago can answer 401 until it propagates to the serving fleet.
429Over the per-minute rate, or past a hard-capped monthly quota. `retry-after` is present on the rate-limit case only.

Response body

WebSearchResponse

NameTypeDescription
facetsobjectPresent only when facets=true
moderequired"keyword" | "semantic" | "hybrid"The mode actually used
partialbooleantrue 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.
resultsrequiredobject[]
routedrequiredbooleantrue when the router chose the vertical, false when you named it
totalrequiredinteger
verticalstring | nullThe 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.