# ReadX Verified Followers API

> ReadX Verified Followers 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-12).

Returns a paginated list of verified (blue-verified or legacy-verified) followers for a given X/Twitter username

## Facts

- Endpoint: GET https://readx.sh/api/%7Bname%7D/verified_followers
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-verified-followers-api-7397d2e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J5BJQcHas9wa70_lJaEI5

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-verified-followers-api-7397d2e6
```

Example prompt: Can you pull the verified followers of the X account @elonmusk using ReadX — I want to see which blue-verified accounts are following him, with their follower counts?

## When to prefer this

Use this endpoint when you need specifically verified (blue-check or legacy-verified) followers for an X/Twitter user, without managing X API keys or OAuth credentials. Ideal for influencer vetting, audience quality analysis, or social proof research. Prefer over direct X API calls when you want pay-per-call micropayment billing with no subscription commitment.

## Known failure modes

- Unknown or suspended username returns empty results or 404-equivalent
- Invalid or expired cursor causes pagination to restart or error
- Rate limits or upstream X API outages may cause 5xx responses
- Payment failure (insufficient USDC balance) blocks the call before it reaches X
- Non-existent user returns empty followers array with has_more: false

## 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 a paginated list of verified followers, each with their user ID, URL, display name, username, follower count, following count, verification flags (isVerified, isBlueVerified), plus a next_cursor string for fetching subsequent pages and a user_count total.

## 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": 200
  },
  "pagination": {
   "has_more": true,
   "next_cursor": "DAABCgABG...cursor"
  }
 }
}
```

## More

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