2s.io Agent Memory List

x402

2s.io Agent Memory List is a paid API for AI agents from 2s.io, paid per call via x402, $0.001200/call, status unknown (last checked 2026-09-15).

Lists keys in the calling agent's memory namespace with cursor pagination, returning metadata only (key, etag, size, timestamps) newest-first.

Price / call$0.001200

Seller volume →—

Success0%

StatusUnknown

How this service works

The (most) everything API: one pay-per-call API giving AI agents ground-truth data across hundreds of endpoints — public records, finance, crypto, security, legal, health, geo, and EDI. USDC via x402, no signup, no API keys.

Output

Returns a paginated list of memory key metadata objects (key name, etag, sizeBytes, createdAt, updatedAt) sorted newest-first, plus a nextCursor string to fetch the next page. Does not return the stored values themselves — use agent.memory.get for values.

Example use cases

Audit agent memory storage usage

“List all the keys in my agent's memory namespace sorted by size, so I can see what's taking up the most space and clean up if needed.”

Find recent conversation cache entries

“Show me the keys I've stored in memory from the last 24 hours, paginating through them so I can review what conversations my agent has cached.”

Discover saved user context prefixes

“What keys do I have saved in my agent memory that start with 'user_'? Page through them so I can understand what user data I'm persisting.”

Technical details

Endpoint

GEThttps://2s.io/api/agent/memory/list

When to prefer

Use this endpoint when an agent needs to enumerate or discover what keys exist in its own memory namespace before deciding which entries to fetch, delete, or update. Prefer this over agent.memory.get when you don't know the exact key name and need to search or browse by prefix.

Side effects

Invalid cursor returns 400 bad request
limit out of range (1-100) returns 400
Unauthorized if x402 signing key does not match namespace
Empty result set with no nextCursor when namespace has no keys or prefix matches nothing
Network timeout on large namespaces

Input

{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "limit": 50,
      "prefix": "session_"
    }
  }
}

Schema · Request body

Field	Type	Description
inputrequired	object

Output

{
  "data": {
    "items": [],
    "nextCursor": null
  },
  "meta": {
    "cost": {
      "usd": 0.0012,
      "tier": 0
    },
    "caller": "x402",
    "version": null,
    "endpoint": "agent.memory.list",
    "settlement": {
      "txHash": "0x1b154398b515f076b5034562c706df0b1b2718decbb76d3b67f281ec690f7d7f",
      "network": "eip155:8453",
      "success": true
    }
  }
}

Reviews

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"

How this service works

Output

Example use cases

Audit agent memory storage usage

“List all the keys in my agent's memory namespace sorted by size, so I can see what's taking up the most space and clean up if needed.”

Find recent conversation cache entries

“Show me the keys I've stored in memory from the last 24 hours, paginating through them so I can review what conversations my agent has cached.”

Discover saved user context prefixes

“What keys do I have saved in my agent memory that start with 'user_'? Page through them so I can understand what user data I'm persisting.”

Technical details

Endpoint

GEThttps://2s.io/api/agent/memory/list

When to prefer

Side effects

Invalid cursor returns 400 bad request
limit out of range (1-100) returns 400
Unauthorized if x402 signing key does not match namespace
Empty result set with no nextCursor when namespace has no keys or prefix matches nothing
Network timeout on large namespaces

Input

{
  "input": {
    "type": "http",
    "method": "GET",
    "queryParams": {
      "limit": 50,
      "prefix": "session_"
    }
  }
}

Schema · Request body

Field	Type	Description
inputrequired	object

Output

{
  "data": {
    "items": [],
    "nextCursor": null
  },
  "meta": {
    "cost": {
      "usd": 0.0012,
      "tier": 0
    },
    "caller": "x402",
    "version": null,
    "endpoint": "agent.memory.list",
    "settlement": {
      "txHash": "0x1b154398b515f076b5034562c706df0b1b2718decbb76d3b67f281ec690f7d7f",
      "network": "eip155:8453",
      "success": true
    }
  }
}