# Agent Memory API – Delete Memory

> Agent Memory API – Delete Memory is a paid API for AI agents from agent-memory-api-bix5.onrender.com, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Permanently deletes a specific encrypted memory entry for an AI agent, with a required reason for audit purposes.

## Facts

- Endpoint: POST https://agent-memory-api-bix5.onrender.com/api/memory/delete
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-memory-api-delete-memory-c65e93a4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_V4oV0w3CZD0NrMBOrkc4A

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 agent-memory-api-delete-memory-c65e93a4 -d '<json body>'
```

Example prompt: Delete memory ID 'mem_abc123' for agent 'agent_007' from the encrypted agent memory store — the reason is that it contains outdated user preferences that are no longer valid.

## When to prefer this

Use this endpoint when an AI agent needs to permanently remove a specific memory entry from its encrypted memory store, particularly when an audit trail of the deletion reason is required. Prefer this over a general data wipe when targeting a single memory_id with traceability.

## Known failure modes

- Missing required fields (agent_id, memory_id, or reason) returns a 400 validation error
- Memory ID not found for the given agent returns a 404 not found error
- Payment not provided or insufficient USDC balance causes a 402 payment required error
- Unauthorized agent attempting to delete another agent's memory returns 403
- Service unavailable on Render.com cold start causes timeout or 503

## How this service works

Pay-per-request encrypted memory APIs for autonomous AI agents using x402. Store, recall, and audit AI agent memory with AES-256 encryption. Built for USDC/Base payments and Japanese AI agent workflows.

## Output

A confirmation response indicating whether the specified memory entry was successfully deleted, along with potential audit metadata about the deletion event.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "reason",
  "agent_id",
  "memory_id"
 ],
 "properties": {
  "reason": {
   "type": "string"
  },
  "agent_id": {
   "type": "string"
  },
  "memory_id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-memory-api-delete-memory-c65e93a4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-memory-api-bix5.onrender.com](https://www.zero.xyz/host/agent-memory-api-bix5.onrender.com/llms.txt)