# x402-vector Memory Retrieval

> x402-vector Memory Retrieval is a paid API for AI agents from api.x402vector.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Retrieves a stored memory value by key from a pay-per-request vector/key-value store designed for AI agents, with no account or API key required.

## Facts

- Endpoint: GET https://api.x402vector.com/v1/memory/%7Bkey%7D?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-vector-memory-retrieval-fcd32b96
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PS6d03Wepqs0wExFf3Ykn

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 x402-vector-memory-retrieval-fcd32b96
```

Example prompt: Can you pull up the memory stored under the key 'project:last-brief' from x402-vector so we can pick up where we left off?

## When to prefer this

Choose this endpoint when an AI agent needs to retrieve previously stored memory or context without managing API keys or subscriptions — ideal for stateless agents that persist context between sessions using a crypto wallet for pay-per-use access. Prefer over traditional vector DBs when the agent needs zero-setup durable storage billed per call.

## Known failure modes

- Key not found — returns empty or 404 if the requested key does not exist in the namespace
- Payment failure — if the x402 micropayment of $0.001 USDC is not completed, the request is rejected
- Invalid key format — malformed key string may result in an error
- Namespace mismatch — accessing a key under the wrong wallet namespace returns no result
- Network/service unavailability — transient errors if the vector store backend is down

## How this service works

A vector database agents pay for by the request. No accounts, no API keys, no subscriptions — just a wallet.

## Output

Returns a JSON object containing the key, the stored value (e.g. a text preference or context blob), the source type (e.g. 'durable'), the namespace (wallet address), and a content hash for integrity verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "key": "project:last-brief",
  "value": {
   "text": "The user prefers concise implementation plans and exact file references."
  },
  "source": "durable",
  "namespace": "0x1111111111111111111111111111111111111111",
  "contentHash": "3f786850e387550fdab836ed7e6dc881de23001b"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-vector-memory-retrieval-fcd32b96/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.x402vector.com](https://www.zero.xyz/host/api.x402vector.com/llms.txt)