# ReadX List Members

> ReadX List Members is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-16).

Returns a paginated list of user members belonging to a specific X/Twitter list, identified by list ID.

## Facts

- Endpoint: GET https://readx.sh/api/lists/:id/members
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-list-members-f320073f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MtnzZEUyLspRn85tKY07Q

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 readx-list-members-f320073f
```

Example prompt: Can you fetch all the members of X list 84839422 for me? Page through all of them using the cursor until there are no more results.

## When to prefer this

Use this endpoint when you need to enumerate the user accounts that are members of a specific X/Twitter list by its numeric ID, especially when you need full pagination support via cursor to retrieve large lists. Prefer this over general search or profile endpoints when the input is a list ID and the goal is membership enumeration.

## Known failure modes

- Invalid or non-numeric list ID returns an error
- List does not exist or is private returns 404 or empty result
- Invalid cursor value causes pagination error
- Rate limit exceeded returns 429 or payment-related error
- Malformed request missing required id parameter

## How this service works

The users that belong to a list (paginate with cursor until has_more is false). Example: GET /api/lists/84839422/members

## Output

Returns a paginated set of user profiles that belong to the specified X/Twitter list, along with pagination metadata including a cursor for the next page and a has_more boolean to indicate whether additional pages exist.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "pattern": "^[0-9]+$",
       "description": "Numeric resource id."
      },
      "cursor": {
       "type": "string",
       "description": "Pagination cursor from a previous response's pagination.next_cursor (the conversation endpoint at /api/{name}/tweets/{id} instead takes its own nested reply cursor — see that endpoint)."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-list-members-f320073f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.sh](https://www.zero.xyz/host/readx.sh/llms.txt)