# ManyLives Vector Memory Add

> ManyLives Vector Memory Add is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-10).

Stores text items with optional metadata into a named vector memory namespace for later semantic retrieval by AI agents

## Facts

- Endpoint: POST https://api.manylives.me/paid/memory/vector-add?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-vector-memory-add-da05cd5d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xUh-jgJ-P1NIaTxeXxVg1

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 manylives-vector-memory-add-da05cd5d -d '<json body>'
```

Example prompt: Save this note to my agent's vector memory under the namespace 'research': 'Supplier B quoted the lowest price for 500 units.' — tag it with source 'email' and ID 'note-1' so I can update it later.

## When to prefer this

Use this endpoint when an AI agent needs persistent, semantically searchable memory across sessions — especially for trading agents building up notes, observations, or research over time. Prefer this over plain key-value stores when the content will later be retrieved by semantic similarity rather than exact key lookup. Ideal for agents that need to accumulate knowledge incrementally and upsert entries by ID without duplicating data.

## Known failure modes

- Text exceeds 4,000 character limit per item — request rejected
- Namespace not found or invalid — defaults to 'default' namespace
- Storage limit of 2,000 items reached — further adds rejected
- Payment not included or insufficient USDC — 402 response returned
- Malformed items array — 400 validation error
- Item ID collision with incompatible schema — upsert may overwrite existing item

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

Returns a JSON object with the list of stored item IDs (including auto-generated ones for items without an explicit ID), total items stored in this call, total items in the wallet/namespace, the namespace name, and the storage limit (max 2,000 items).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "items": {
   "type": "string",
   "examples": [
    [
     {
      "id": "note-1",
      "meta": {
       "source": "email"
      },
      "text": "Supplier B quoted the lowest price for 500 units."
     }
    ]
   ],
   "description": "array of {text (required, max 4,000 chars), id (optional, reuse to update), meta (optional JSON)}"
  },
  "namespace": {
   "type": "string",
   "description": "optional group name (default 'default')"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ids": [
   "note-1",
   "v_k3m8q2r7t9w4"
  ],
  "limit": 2000,
  "stored": 2,
  "namespace": "default",
  "items_in_wallet": 2
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-vector-memory-add-da05cd5d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)