Skip to main content
POST
Lexically query one subject's candidates
Run bounded lexical search over one subject’s isolated Praxa memory candidates with provider and record-kind filters.
Availability: Qualification preview. Required scope: memory:read.

Authenticate safely

Create a disposable personal workspace API key with exactly memory:read. Send it as Authorization: Bearer $PRAXA_API_KEY. A Gateway OAuth token, Supabase JWT, provider credential, or organization memory key is not interchangeable with this key. The hosted playground sends the credential from your browser session to the documented API through the configured playground proxy. Use test data, never share the key, and revoke it when the check ends.

Request fields

v1
required
apiVersion request field.
string
required
subject request field.
string
required
query request field.
array<mem0 | zep | graphiti | langgraph | letta | openai_agents | custom>
providerIds request field.
array<message | fact | summary | episode | pinned_context | document | entity | edge>
kinds request field.
integer
limit request field.

Runnable request examples

What success means

A 200 response contains subject-scoped lexical matches. It is not vector, semantic, or graph recall.

Successful response

200 — Bounded lexical matches for the requested subject.
v1
required
apiVersion response field.
lexical
required
retrievalMode response field.
array<object>
required
data response field.

Handle failures

Example problem

Verify the result

  1. Require retrievalMode: "lexical".
  2. Confirm every result matches the requested subject and filters.
  3. Query a second subject and tenant and require isolation.

Retry, cleanup, and production use

  • Treat 401, 403, and 409 as authority or state signals, not generic retry prompts.
  • For 429 or retryable 5xx responses, follow server retry guidance and keep a bounded attempt budget.
  • Move the request into a trusted application backend before production; never ship the Praxa key in browser or mobile code.
  • Revoke the disposable key, disable test webhooks, and erase disposable candidate data after validation.
Continue with API authentication, the failure and retry guide, and the end-to-end coverage matrix.
Last modified on August 14, 2026