# Vaaya Zep Memory Search

> Vaaya Zep Memory Search is a paid API for AI agents from vaaya.ai, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Searches a user's Zep memory graph for relevant nodes, edges, or episodes using a natural language query

## Facts

- Endpoint: POST https://vaaya.ai/api/run/zep/search
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vaaya-zep-memory-search-dd34eae5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZwFtWr9hFMghwUODUIOIX

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability vaaya-zep-memory-search-dd34eae5 -d '<json body>'
```

Example prompt: Search user 'user_abc123' in Zep memory for anything related to 'project deadlines', looking through nodes, and return up to 10 results.

## When to prefer this

Use this endpoint when an AI agent needs to retrieve relevant memory context for a specific user from a Zep memory graph — especially when you need to search across nodes, edges, or episodes using natural language. Prefer this over generic vector search when you already have a user_id and want to leverage Zep's structured memory model with scoped retrieval.

## Known failure modes

- Missing required 'query' field returns validation error
- Missing 'user_id' returns validation error
- Invalid 'scope' enum value causes rejection
- Empty or whitespace-only query rejected (minLength:1)
- Limit exceeds maximum of 50 causes schema validation error
- User ID not found in Zep returns empty results
- Payment not included or insufficient USDC balance causes 402 error

## How this service works

Give an AI agent a credit account. Set a limit and a spending policy, and the agent makes approved, metered purchases from providers that accept Vaaya.

## Output

Returns a list of matching memory entries (nodes, edges, or episodes) from the user's Zep memory graph that are semantically relevant to the provided query, based on the selected scope.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json",
      "form-data",
      "text"
     ]
    },
    "body": {
     "type": "object",
     "properties": {
      "query": {
       "type": "string",
       "minLength": 1
      },
      "user_id": {
       "type": "string",
       "minLength": 1
      },
      "scope": {
       "type": "string",
       "enum": [
        "edges",
        "nodes",
        "episodes"
       ]
      },
      "limit": {
       "type": "integer",
       "exclusiveMinimum": 0,
       "maximum": 50
      }
     },
     "required": [
      "query",
      "user_id"
     ],
     "additionalProperties": true,
     "$schema": "http://json-schema.org/draft-07/schema#"
    },
    "pathParams": {
     "type": "object"
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   },
   "required": [
    "type"
   ]
  }
 },
 "required": [
  "input"
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vaaya-zep-memory-search-dd34eae5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from vaaya.ai](https://www.zero.xyz/host/vaaya.ai/llms.txt)