# SYAR Memory Query

> SYAR Memory Query is a paid API for AI agents from syar-memory-proxy.lorenzo-amirante98.workers.dev, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).

Semantically query long-term agent memories isolated by wallet address, returning relevant stored memories for a given search query.

## Facts

- Endpoint: POST https://syar-memory-proxy.lorenzo-amirante98.workers.dev/memory-query
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/syar-memory-query-8f4b0cbd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_na1RlxnZGjuIugzEQrawe

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 syar-memory-query-8f4b0cbd -d '<json body>'
```

Example prompt: Search my SYAR memory store for anything I've previously remembered about 'project deadlines' and return the top 3 most relevant memories.

## When to prefer this

Choose this endpoint when an AI agent needs to semantically search its own isolated long-term memory store, retrieving past memories relevant to a current task or query. It is ideal for agents that previously wrote memories to the SYAR service and need to recall context across sessions, with per-wallet isolation ensuring memories are private to each agent. Prefer this over generic vector databases when you need a ready-made, pay-per-call semantic memory service without managing your own infrastructure.

## Known failure modes

- Missing required 'query' field returns a 400 validation error
- No matching memories found returns an empty 'memories' array
- Payment not provided or insufficient (x402 payment required at $0.005 USDC) results in a 402 Payment Required response
- Invalid limit value may cause a 400 error
- Wallet not recognized or no memories written yet returns empty results
- Cloudflare Worker timeout or downtime returns a 5xx error

## How this service works

Semantic memory service payable via x402. Agents can write and query long-term memories isolated by wallet.

## Output

Returns a JSON object containing a 'memories' array of memory objects semantically relevant to the query, ranked by relevance, up to the specified limit (default 5). Each memory object contains the stored memory data associated with the querying wallet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "query"
 ],
 "properties": {
  "limit": {
   "type": "integer",
   "description": "Max number of results to return (default 5)"
  },
  "query": {
   "type": "string",
   "description": "The search query text"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "memories"
 ],
 "properties": {
  "memories": {
   "type": "array",
   "items": {
    "type": "object"
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/syar-memory-query-8f4b0cbd/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from syar-memory-proxy.lorenzo-amirante98.workers.dev](https://www.zero.xyz/host/syar-memory-proxy.lorenzo-amirante98.workers.dev/llms.txt)