# ReadX List Metadata Lookup

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

Fetches a Twitter/X list's metadata including name, owner, description, and member count by numeric list ID

## Facts

- Endpoint: GET https://readx.sh/api/lists/:id
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-list-metadata-lookup-f8d0c335
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DGel9WJU9-fi4cf-dgKSj

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-metadata-lookup-f8d0c335
```

Example prompt: Can you pull up the metadata for Twitter list number 1 — I want to see its name, who owns it, what the description says, and how many members are in it?

## When to prefer this

Use this endpoint when you need structured JSON metadata about a specific Twitter/X list and you already know the numeric list ID. Prefer this over scraping Twitter directly or using the full Twitter API when you want pay-per-call pricing with no subscription overhead.

## Known failure modes

- List ID not found or does not exist — returns 404 or empty response
- Non-numeric list ID provided — schema validation rejects the request
- List is private or restricted — access may be denied
- Payment not processed — x402 payment required before data is returned
- Rate limiting or upstream X/Twitter API unavailability

## How this service works

A list's metadata (name, owner, description, member count). Example: GET /api/lists/1

## Output

Returns a JSON object containing the list's name, owner profile, description text, and member count for the requested numeric list ID.

## 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."
      }
     }
    }
   },
   "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-metadata-lookup-f8d0c335/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)