browse: browse without a query

Behaviour

For 'what is new here' rather than 'find me X'.

Costs 1 credit.

inputSchema

Name	Type
`limit`	integer
`sort`	"recency" \| "host_rank" \| "quality" \| "published" \| "words" \| "centrality"
`vertical`	string

A JSON payload in the text content block, and the same payload as structuredContent for clients that support it.

outputSchema

Name	Type	Description
`facets`	object	Present only when facets=true
`mode`required	"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.
`results`required	object[]	—
`routed`required	boolean	true when the router chose the vertical, false when you named it
`total`required	integer	—
`vertical`	string \| null	The vertical actually queried

Over Streamable HTTP, with the required arguments filled in:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "browse",
    "arguments": {}
  }
}

Most clients do this for you — see Connect a client. To drive it by hand, complete the startup lifecycle first.

If your client does not speak MCP, this capability is GET /browse, taking the same parameters and returning the same body.

curl -H "x-api-key: $UNLOB_API_KEY" \
  "https://api.unlob.com/browse"