Skip to main content
GET
Search graph node content
Find knowledge-graph nodes whose stored content matches q and return their ids. This is a full-text match over chunk text, which the graph payload the browser holds does not carry, so it finds nodes a title-only search bar would miss without shipping content to the client. Scoped to the effective subject. A query with no usable search terms returns an empty list rather than an error.

Authorization

This route requires the read scope. A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.

Headers

These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.

Success responses

Errors

Every error is an RFC 9457 application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.

Authorizations

X-Exo-API-Key
string
header
required

An Exo API key (exo_...) sent as the X-Exo-API-Key header.

Query Parameters

q
string
required
Required string length: 2 - 200
limit
integer
default:500
Required range: 1 <= x <= 2000

Response

The ids of the matching nodes.

The response is of type Response Recall Graph Search V1 Recall Graph Search Get · object.