# ReadX — Twitter/X Followers Web API

> ReadX — Twitter/X Followers Web API is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Returns a paginated list of followers for a given Twitter/X username, with full profile details for each follower

## Facts

- Endpoint: GET https://readx.sh/api/%7Bname%7D/followers_web
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-twitter-x-followers-web-api-d779fd24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_x3dHdIrWx9qC-0UOOpNNZ

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-twitter-x-followers-web-api-d779fd24
```

Example prompt: Can you pull the followers list for the Twitter account 'jack' — I want to see who's following him, with their bios and follower counts?

## When to prefer this

Choose this endpoint when you need structured follower data for a Twitter/X account without managing Twitter API keys or OAuth credentials. It is ideal for agents that need to enumerate followers programmatically, build social graphs, or analyze audience composition. Prefer it over the Twitter official API when you want pay-per-call micropayment pricing (no monthly subscription), or when Twitter API tier limits are a constraint. Use the verified-followers sibling endpoint instead if you only want verified followers.

## Known failure modes

- Invalid or non-existent username returns error code
- Payment not included or insufficient USDC results in 402 Payment Required
- Rate limiting or upstream X/Twitter API restrictions may cause failures
- Protected account followers may not be accessible
- Expired or invalid pagination cursor returns error
- Network timeout on large follower lists

## How this service works

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

## Output

A JSON object containing an array of follower user profiles (each with id, username, fullname, bio, location, follower/following counts, tweet count, profile picture, banner, website, join date, verified type, protected/suspended status, and pinned tweet), a total_count, and pagination metadata (has_more boolean and next_cursor string for fetching subsequent pages, ~200 users per page).

## 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": {
   "users": [
    {
     "id": "12",
     "bio": "",
     "likes": 0,
     "media": 0,
     "banner": "",
     "tweets": 30000,
     "userPic": "",
     "website": "",
     "fullname": "jack",
     "joinDate": 1142974214,
     "location": "",
     "username": "jack",
     "followers": 6500000,
     "following": 4000,
     "protected": false,
     "suspended": false,
     "pinnedTweet": "0",
     "verifiedType": "Blue"
    }
   ],
   "total_count": 70
  },
  "pagination": {
   "has_more": true,
   "next_cursor": "DAABCgABG...cursor"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-twitter-x-followers-web-api-d779fd24/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)