# SYAR Memory Write

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

Stores a text memory entry with optional metadata, isolated by wallet, into a semantic long-term memory store payable via x402.

## Facts

- Endpoint: POST https://syar-memory-proxy.lorenzo-amirante98.workers.dev/memory-write
- Price: $0.001/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-write-9815f14d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ghOVkJ6qqDyy-aOPprV-G

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-write-9815f14d -d '<json body>'
```

Example prompt: Remember that my preferred meeting time is Tuesday mornings at 10am and I dislike video calls — store that as a memory entry so you can recall it later.

## When to prefer this

Choose this endpoint when you need to persist agent memories or context in a wallet-isolated semantic store that is payable per-call via x402. Ideal for autonomous agents that need durable, cross-session memory without managing their own database, particularly when operating in a micropayment-native environment where per-call USDC billing is acceptable.

## Known failure modes

- Missing required 'content' field returns a validation error
- Payment not included or insufficient USDC via x402 results in 402 Payment Required
- Malformed metadata object may cause rejection or silent drop of metadata
- Wallet not identified in payment header causes memory isolation failure
- Network timeout on Cloudflare Worker edge node returns 503

## 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 UUID for the newly created memory entry (id) and a confirmation status field set to 'stored', allowing the agent to reference or verify the write.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "content"
 ],
 "properties": {
  "content": {
   "type": "string",
   "description": "Text content of the memory entry to store"
  },
  "metadata": {
   "type": "object",
   "description": "Optional metadata object attached to the memory entry"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "a1b2c3d4-uuid",
  "status": "stored"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/syar-memory-write-9815f14d/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)