# Agent Persistent Memory - List All Keys

> Agent Persistent Memory - List All Keys is a paid API for AI agents from jp-data-api-production.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Lists all keys stored in a named namespace, returning sizes and timestamps for each stored memory entry.

## Facts

- Endpoint: GET https://jp-data-api-production.up.railway.app/memory/list
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-persistent-memory-list-all-keys-6f46c145
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lbkASQeMhuZCayLoyaaQn

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-persistent-memory-list-all-keys-6f46c145
```

Example prompt: Show me all the keys I have stored in the 'agent-session-42' namespace, including their sizes and timestamps.

## When to prefer this

Use this endpoint when an agent needs to discover or audit what keys already exist in a persistent memory namespace before performing get or set operations. Ideal for memory management, debugging, or when the agent needs to enumerate stored state without knowing exact key names in advance.

## Known failure modes

- Missing 'ns' query parameter — returns error indicating namespace is required
- Namespace does not exist or is empty — may return an empty list or 404
- Payment not processed or insufficient funds — x402 payment required error
- Service unavailable on Railway — 502/503 gateway error

## How this service works

List all keys stored in your namespace, with sizes and timestamps. Companion to /memory/set and /memory/get for agent persistent memory.

## Output

A list of all keys within the specified namespace, each with its associated size (in bytes or similar unit) and timestamp indicating when it was stored or last updated. This gives agents a complete inventory of what is currently held in persistent memory.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "ns"
     ],
     "properties": {
      "ns": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-persistent-memory-list-all-keys-6f46c145/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from jp-data-api-production.up.railway.app](https://www.zero.xyz/host/jp-data-api-production.up.railway.app/llms.txt)