# JP Data API – Persistent Key-Value Memory Read

> JP Data API – Persistent Key-Value Memory Read 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).

Retrieves a previously stored value from persistent key-value memory by namespace and key, enabling AI agents to recall long-term state across sessions.

## Facts

- Endpoint: GET https://jp-data-api-production.up.railway.app/memory/get
- 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/jp-data-api-persistent-key-value-memory-read-4f52251b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mw_hucqPNkZLAkRvCxQrX

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 jp-data-api-persistent-key-value-memory-read-4f52251b
```

Example prompt: Can you read back the value I stored in my agent's persistent memory under namespace 'project-alpha' with key 'last-completed-step'?

## When to prefer this

Use this endpoint when an AI agent needs to recall previously stored state, task progress, or data across sessions without setting up a dedicated database. Ideal for lightweight, pay-per-read persistent memory where no signup or infrastructure management is required. Prefer this over general-purpose databases when cost-per-call micro-billing via x402 is acceptable and the data was stored using the companion /memory/set endpoint on the same service.

## Known failure modes

- Key or namespace not found — returns an error or null if the key was never set or has expired
- Missing required query parameters (ns or key) — returns a 400-level validation error
- Payment failure — request rejected if the $0.001 USDC x402 payment is not included or invalid
- Stale or overwritten data — if another agent session overwrote the key, the returned value may not match expectations

## How this service works

Retrieve a value previously stored via /memory/set. Persistent key-value memory for AI agents — no signup, pay per read. Use for agent long-term memory, task state, resuming work across sessions.

## Output

Returns the value previously stored at the specified namespace and key, enabling the agent to reconstruct prior task state, resume interrupted workflows, or access saved data from earlier sessions.

## 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",
      "key"
     ],
     "properties": {
      "ns": {
       "type": "string"
      },
      "key": {
       "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/jp-data-api-persistent-key-value-memory-read-4f52251b/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)