related
Coverage graphReturns the connected neighbourhood of a passage from the coverage graph — the edges are what to read next.
Follow the thread in one call rather than one search per hop. The graph already knows which host published the passage, which story it belongs to, which topics and entities it touches, and what links to it.
An agent can decompose a question across the structure instead of reconstructing that structure from ranked lists inside its context window.
Arguments
| Name | Type | Description |
|---|---|---|
idrequired | string | Seed passage id. |
hops | integer | Traversal depth, bounded breadth-first. |
limit | integer | Neighbour cap. |
Returns:Connected passages, each with the edge type that reached it.
Example
Prompt: “What else is connected to this article?”
{ "id": "p:8f2c9a", "hops": 2, "limit": 15 }Over HTTP
The same operation is available as GET /related for anything that does not speak MCP.
curl -H "x-api-key: $UNLOB_API_KEY" \
"https://api.unlob.com/related?id=p:8f2c9a&hops=2&limit=15"Setup
One config block gives your client all 11 tools, including this one.
{
"mcpServers": {
"unlob": {
"command": "npx",
"args": ["-y", "@unlob/mcp"],
"env": { "UNLOB_API_KEY": "ulb_your_key_here" }
}
}
}Get a key and connect
10,000 free requests a month. MCP calls bill exactly like HTTP calls — one request each.