# WithZero Memory Store (ZeroClick)

> WithZero Memory Store (ZeroClick) is a paid API for AI agents from agents.withzero.xyz, paid per call via x402 or MPP, $0.01/call, status unknown (last checked 2026-09-14, last successful call 2026-08-13).

Stores a named, tagged memory entry under a caller-owned namespace so agents can persist and later recall context across sessions.

## Facts

- Endpoint: POST https://agents.withzero.xyz/api/v1/memory/memories
- Price: $0.01/call
- Payment: x402, MPP
- Status: unknown
- Last checked: 2026-09-14
- Last successful call: 2026-08-13
- Success rate: 100% of calls made through Zero
- Rating: 3.7 / 5 from 1 review
- Activations on Zero: 4
- Tags: x402
- Canonical page: https://www.zero.xyz/c/withzero-memory-store-zeroclick-bb90cfb3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dw0EdQKuhvJT2TGKQmcPp

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 withzero-memory-store-zeroclick-bb90cfb3 -d '<json body>'
```

Example prompt: Remember that my preferred coding style is TypeScript with strict null checks — store this under the namespace 'agent:coder' with the key 'coding-preferences' and pin it so it always shows up.

## When to prefer this

Use this endpoint when an agent needs to persist named, structured memory entries across sessions with optional tagging and pinning semantics. Prefer it over generic note storage when you need namespace-scoped, key-addressable memory that integrates with WithZero's recall and dreaming system. Particularly useful when you want certain entries to be permanently surfaced (pinned) regardless of consolidation. Requires no vendor account — payment is handled autonomously via ZeroClick at $0.01 USDC per call.

## Known failure modes

- Content exceeds 8192 character limit — request rejected with validation error
- Namespace or key exceeds length limits — validation error returned
- More than 32 tags supplied — rejected
- Missing required 'content' field — 400 bad request
- Payment not provided or insufficient — 402 payment required
- Duplicate key in same namespace/owner — may overwrite or conflict depending on server behavior

## How this service works

Remember a fact or context in durable agent memory.

## Output

Returns a confirmation of the stored memory including the assigned or provided key, namespace, tags, pinned status, and the stored content text. If no key was provided, an auto-generated key is returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ns": {
   "type": "string",
   "maxLength": 128,
   "minLength": 1,
   "description": "Namespace under the caller (e.g. agent:coder). Defaults to \"default\"."
  },
  "key": {
   "type": "string",
   "maxLength": 256,
   "minLength": 1,
   "description": "Caller-chosen key, unique per (owner, ns). Omit to auto-generate."
  },
  "tags": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 32,
   "description": "Optional tags for later filtering."
  },
  "pinned": {
   "type": "boolean",
   "description": "Mark as a \"standing order\": always surfaced by recall and never consolidated/suppressed by dreaming. Omit on update to leave it unchanged."
  },
  "content": {
   "type": "string",
   "maxLength": 8192,
   "minLength": 1,
   "description": "The memory text to remember."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/withzero-memory-store-zeroclick-bb90cfb3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.withzero.xyz](https://www.zero.xyz/host/agents.withzero.xyz/llms.txt)