# MolCloud Memory Vault

> MolCloud Memory Vault is a paid API for AI agents from api.molcloud.net, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-17).

Persistent key-value memory store for AI agents supporting set, get, list, search, and delete operations within logical namespaces

## Facts

- Endpoint: POST https://api.molcloud.net/api/memory/vault?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/molcloud-memory-vault-af6d4875
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MmnQxvN0iRXAug46ZYtSu

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 molcloud-memory-vault-af6d4875 -d '<json body>'
```

Example prompt: Save the string 'user prefers dark mode and metric units' under the key 'user-preferences' in the 'settings' namespace with tags ['preferences','ui'] so you can recall it later.

## When to prefer this

Choose this endpoint when an AI agent needs lightweight, pay-per-use persistent memory without managing a dedicated database — ideal for autonomous agents that need to store state, context, or intermediate results across invocations and settle micropayments in USDC via x402. Prefer it over self-hosted solutions when low operational overhead and per-call pricing are priorities.

## Known failure modes

- Key not found on 'get' or 'delete' returns error status
- Invalid action enum value returns validation error
- Missing required 'action' field causes 400-type error
- Payment not included or insufficient USDC causes 402 response
- Namespace isolation prevents cross-namespace key access
- Large value payloads may be rejected or truncated

## How this service works

41 pay-per-request AI, search, headless browser, crypto alpha & memory APIs for autonomous agents settling in USDC on Base via x402 v2.

## Output

A JSON object with a 'status' field ('success' or error) and a 'data' object containing the action performed and the result — for 'set' actions, a 'stored: true' confirmation; for 'get' or 'list' actions, the retrieved value(s); for 'search', matching records; for 'delete', a deletion confirmation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "key": {
   "type": "string",
   "description": "Memory key identifier"
  },
  "tags": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Optional searchable tags"
  },
  "query": {
   "type": "string",
   "description": "Search query when action=\"search\""
  },
  "value": {
   "description": "JSON value or string to store when action=\"set\""
  },
  "action": {
   "enum": [
    "set",
    "get",
    "list",
    "search",
    "delete"
   ],
   "type": "string",
   "description": "Memory vault operation"
  },
  "namespace": {
   "type": "string",
   "default": "default",
   "description": "Logical namespace (default: default)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "action": "set",
   "stored": true
  },
  "status": "success",
  "endpoint": "/api/memory/vault"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/molcloud-memory-vault-af6d4875/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.molcloud.net](https://www.zero.xyz/host/api.molcloud.net/llms.txt)