# ReadX List Lookup API

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

Fetches detailed JSON data for a specific X/Twitter list by its ID, including list metadata and members, paid per call via x402 micropayments.

## Facts

- Endpoint: GET https://readx.sh/api/lists/%7Bid%7D
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-08
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-list-lookup-api-3b51f655
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_i_NSMk_vng024pOnzYeGw

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-lookup-api-3b51f655
```

Example prompt: Can you pull up the details for Twitter list ID 1234567890 — I want to know its name, description, and who owns it?

## When to prefer this

Choose this endpoint when you need programmatic access to X/Twitter list data without managing Twitter API keys or OAuth credentials. Ideal for agents that need occasional, pay-as-you-go access to list metadata on X, especially when integrating with USDC-based micropayment workflows on Base or Solana. Prefer this over the official Twitter API when you want to avoid API key management and subscription tiers.

## Known failure modes

- Invalid or non-existent list ID returns an error code in the JSON response
- List is private and not accessible returns an access error
- Insufficient USDC balance or failed x402 payment results in HTTP 402 with no data returned
- Malformed list ID format causes a bad request error
- Rate limiting or temporary API unavailability returns a server error

## How this service works

ReadX is a read-only X/Twitter JSON API. Profiles, timelines, tweets, search, lists, followers &amp; following — pay per call with x402 micropayments in USDC on Base or Solana. No API keys.

## Output

A JSON object containing list metadata such as list name, description, owner profile, member count, subscriber count, and other list-level attributes for the specified X/Twitter list ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 0,
  "data": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-list-lookup-api-3b51f655/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)
