# Agent Memory Summary API

> Agent Memory Summary API is a paid API for AI agents from agent-memory-api.johntaylor1online.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Retrieves a summarized, scored list of relevant memories from persistent agent memory storage

## Facts

- Endpoint: POST https://agent-memory-api.johntaylor1online.workers.dev/memory/summary
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-memory-summary-api-4ea8279b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OnLUR64yk56dMf4TxYy4g

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-summary-api-4ea8279b -d '<json body>'
```

Example prompt: Can you retrieve a summary of my stored memories that are relevant to our current task, including their relevance scores?

## When to prefer this

Choose this endpoint when an AI agent needs to retrieve and summarize stored memories ranked by relevance, particularly in agent-to-agent or autonomous agent workflows where persistent context across sessions is needed. It is well-suited for agentic applications built on Cloudflare Workers that use x402 micropayment infrastructure. Prefer this over full memory store dumps when you want scored, filtered summaries rather than raw memory enumeration.

## Known failure modes

- Missing required input fields (type or method) returns a validation error
- Poorly formed POST body may return 400 Bad Request
- Payment not received or insufficient USDC balance causes x402 payment required response
- No matching memories found may return an empty memories array
- Cold-start or empty memory store returns zero results
- Worker timeout or upstream failure returns 500 error

## How this service works

x402-powered API: agent-memory-api

## Output

Returns a JSON array of memory objects, each containing a relevance score (e.g. 0.95) and a content string describing the recalled memory, ordered by relevance to the query context.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "memories": [
   {
    "score": 0.95,
    "content": "Memory recall works"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-memory-summary-api-4ea8279b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-memory-api.johntaylor1online.workers.dev](https://www.zero.xyz/host/agent-memory-api.johntaylor1online.workers.dev/llms.txt)