Browse documentation
Connect two passages
Coverage Graph: the shortest chain of edges linking two passages — connect-the-dots retrieval.
get
/path Request
curl \
-H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/path?a=<a>&b=<b>"Behaviour
Returns the node chain between them: passages (p:), hosts (h:), stories (s:), topics (t:), entities (e:). `found: false` means no chain exists within the corpus, which is itself an answer — these two things are not connected in anything we hold.
Parameters
| Name | Type | Description |
|---|---|---|
arequired | string | Start passage id. |
brequired | string | Goal passage id. |
Responses
| Status | Meaning |
|---|---|
200 | The node chain, or found=false when none exists. |
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. |
The same call over MCP is a tool with these parameter names unchanged. See Errors for what to do with each status.