# ReadX Followers Web

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

Returns a paginated list of a Twitter/X user's followers as rendered on the web, ~70 per page, capped at ~800 total

## Facts

- Endpoint: GET https://readx.sh/api/:name/followers_web
- 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-followers-web-546d0aa0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X7As7VfkoSLhBDTriRJ9u

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-followers-web-546d0aa0
```

Example prompt: Can you pull the full list of followers for the X account 'elonmusk' — paginate through all the pages until you have them all?

## When to prefer this

Use this endpoint when you need the web-view follower list for a specific X/Twitter account, especially when you want paginated access up to ~800 followers without needing Twitter's official API credentials. It is ideal for lightweight social graph analysis, influencer research, or audience auditing where the cap of ~800 is sufficient. If you need verified followers only, use the verified followers endpoint on the same service instead.

## Known failure modes

- Unknown or suspended X handle returns 404 or empty result
- Rate limiting or quota exhaustion returns 429 or payment-required error
- Invalid cursor value causes pagination error
- Follower list is private/protected — endpoint may return empty or error
- Cap of ~800 followers reached — has_more remains false even if account has more followers
- Malformed username (e.g. includes '@') rejected by pattern validation

## How this service works

A user's followers as shown on the web (~70 per page, capped at ~800; paginate with cursor until has_more is false). Example: GET /api/jack/followers_web

## Output

A paginated JSON response containing an array of follower account objects (with profile details such as name, handle, bio, follower/following counts) as displayed on the X web interface, along with pagination metadata including a next_cursor and a has_more boolean flag indicating 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": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_]+$",
       "minLength": 1,
       "description": "X handle without the leading @ (alphanumeric and underscore)."
      },
      "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-followers-web-546d0aa0/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)