Search - Exo

What this family does

Search is the cheap primitive. It runs pgvector and BM25 over the organization’s memory chunks and fuses the two rankings, then stops. There is no brain inference, no cognition block and no contradiction detection. Reach for it when you want matching text and you already know what you are going to do with it. Reach for POST /v1/retrieve when you want Exo to reason.

Routes

Method	Path	Scope	What it does
`POST`	`/v1/search`	`read`	Lean hybrid search

Headers that apply here

Neither header is declared as an OpenAPI parameter, so neither appears in the generated schema tables.

X-Exo-Subject selects which subject the call acts for on the subject-aware routes above. Omit it to act as the key owner. See Subjects.

The shape of a call

Search stored content.

curl -X POST https://api.get-exo.com/v1/search \
  -H "X-Exo-API-Key: $EXO_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "pricing model", "scope": "user", "topK": 10}'

import httpx

response = httpx.post(
    "https://api.get-exo.com/v1/search",
    headers={"X-Exo-API-Key": EXO_KEY},
    json={"query": "pricing model", "scope": "user", "topK": 10},
)
for hit in response.json()["results"]:
    print(hit["score"], hit["title"])

const response = await fetch("https://api.get-exo.com/v1/search", {
  method: "POST",
  headers: {
    "X-Exo-API-Key": process.env.EXO_KEY!,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ query: "pricing model", scope: "user", topK: 10 }),
});
const { results } = await response.json();

The response:

{
  "results": [
    {
      "chunk": "We agreed to drop the freemium tier and price on usage.",
      "nodeId": "ingest:4a1e88f0-9c2d-4f31-b7a0-5e6c1d820b93:7d3c9b1e04a2",
      "title": "Pricing working session",
      "score": 0.031746
    }
  ],
  "usage": { "readUnits": 1, "embedTokens": 4 }
}

Traps

scope is a body field. user filters to the effective subject, org searches the whole organization. This is separate from the X-Exo-Subject header, which decides which subject user means. Search meters its own rate-limit family. It embeds the query on every call, so it does not draw on the generous reads bucket.

API reference

Base URL, authentication, and the conventions every route shares.

Errors

The problem envelope and the full code catalogue.

​What this family does

​Routes

​Headers that apply here

​The shape of a call

​Traps

​Related