# AgentBit List/Queue Memory

> AgentBit List/Queue Memory is a paid API for AI agents from agentbit.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-23).

Provides a private, ordered list/queue data structure for agents with push, pop, peek, range, length, and clear operations scoped to the paying wallet.

## Facts

- Endpoint: POST https://agentbit.app/v1/memory/list?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentbit-list-queue-memory-097da0ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RhXqkPTnRobstaujTdPLC

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 agentbit-list-queue-memory-097da0ec -d '<json body>'
```

Example prompt: Push the task 'send_weekly_report' onto the tail of my 'pending_tasks' list in the 'reporting' namespace, and set it to expire in 86400 seconds.

## When to prefer this

Choose this endpoint when your AI agent needs a persistent, ordered data structure (queue, stack, or list) that survives between invocations and is scoped to a specific wallet identity. Ideal for task queues, event buffers, breadcrumb logs, and any workflow requiring FIFO or LIFO ordering. Prefer over key-value storage when order and position matter.

## Known failure modes

- Invalid operation enum value returns a 400 error
- Missing required 'key' or 'operation' fields returns a validation error
- Expired TTL causes list to be unavailable
- Attempting to pop from an empty list returns null or empty response
- Payment failure (x402) blocks the operation
- TTL exceeding 90-day maximum is rejected

## How this service works

Private ordered list/queue for an agent: push/pop/peek/range/length/clear, scoped to the paying wallet. For task queues, event logs, buffers.

## Output

Returns a JSON response containing the operation result — the pushed/popped/peeked value, a list of items for range queries, an integer for length, or a success confirmation for clear/push operations. Includes the current list length where applicable.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "end": {
   "enum": [
    "head",
    "tail"
   ],
   "type": "string",
   "description": "Which end to push/pop/peek (default tail)."
  },
  "key": {
   "type": "string",
   "description": "The list name."
  },
  "count": {
   "type": "integer",
   "description": "For range: how many items (default 100)."
  },
  "start": {
   "type": "integer",
   "description": "For range: start index (negative counts from the end)."
  },
  "value": {
   "description": "Any JSON value to push (for push)."
  },
  "namespace": {
   "type": "string",
   "description": "Optional group (default \"default\")."
  },
  "operation": {
   "enum": [
    "push",
    "pop",
    "peek",
    "range",
    "length",
    "clear"
   ],
   "type": "string",
   "description": "What to do."
  },
  "ttl_seconds": {
   "type": "integer",
   "description": "Optional expiry in seconds (max 90 days)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentbit-list-queue-memory-097da0ec/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentbit.app](https://www.zero.xyz/host/agentbit.app/llms.txt)
