# Port 402 Memory Read

> Port 402 Memory Read is a paid API for AI agents from port-402-production.up.railway.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-31).

Retrieves a stored value from a persistent key-value memory store for an AI agent, paid per-call via x402 micropayment.

## Facts

- Endpoint: GET https://port-402-production.up.railway.app/v1/memory/%7Bkey%7D?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/port-402-memory-read-f7223c8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ESZwDWrQDGVQ839aYslLK

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 port-402-memory-read-f7223c8a
```

Example prompt: Retrieve what I stored in my agent memory under the key 'notes' and tell me what's there.

## When to prefer this

Use this endpoint when an AI agent needs to retrieve a specific named value from its own persistent key-value memory store and knows the exact key. Prefer this over the list-keys endpoint when you already know the key name and want a direct lookup. Ideal for stateful agentic workflows where agents persist intermediate state, user preferences, or task context between sessions, and want to recall it in a future call without maintaining local state.

## Known failure modes

- Key not found: returns an error or null value if the specified key does not exist in memory
- Invalid key format: malformed key string may result in a bad request response
- Payment failure: x402 micropayment not completed or insufficient USDC balance causes the call to be rejected
- Unauthorized access: attempting to read a key belonging to a different agent session may be denied
- Service unavailability: Railway-hosted backend downtime may cause 5xx errors

## How this service works

Pay-per-use infrastructure for autonomous AI agents. No account, no API key: pay each call with x402.

## Output

Returns a JSON object containing the requested memory key and its associated stored value, e.g. {"key": "notes", "value": {"task": "remember this"}}. If the key exists, the full value object is returned. Payment of $0.001 USDC is charged per successful call via x402.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "key": "notes",
  "value": {
   "task": "remember this"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/port-402-memory-read-f7223c8a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from port-402-production.up.railway.app](https://www.zero.xyz/host/port-402-production.up.railway.app/llms.txt)