Back to Browse
Port 402 Memory Read
x402
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.
Price / call$0.001
Success—
StatusUnknown
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.
Example use cases
Resuming a task mid-session
“I need to pick up where I left off — can you read back whatever is stored in my agent memory under the key 'current_task' so we can continue?”
Checking a saved preference
“Look up what I stored in my persistent memory under the key 'user_preferences' and tell me what it says.”
Verifying a previously remembered value
“Did I save anything under the key 'meeting_notes' in my agent memory? If so, what does it say?”
Technical details
Endpoint
GEThttps://port-402-production.up.railway.app/v1/memory/%7Bkey%7D?utm_source=zero.xyzWhen to prefer
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.
Side effects
- 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
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| properties | string |
Output
Schema · Response
{
"type": "json",
"example": {
"key": "notes",
"value": {
"task": "remember this"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"