# Surf Twitter – User Followers

> Surf Twitter – User Followers is a paid API for AI agents from twitter.surf.cascade.fyi, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-09).

Fetches the list of followers for a given Twitter/X user, returning follower names, usernames, and follower counts.

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/users/%7Bref%7D/followers
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-09
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/surf-twitter-user-followers-cad4b4b2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QLdvKIADMgzBj4-bc0Blc

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 surf-twitter-user-followers-cad4b4b2
```

Example prompt: Can you pull the followers list for the Twitter account @elonmusk using Surf Twitter's pay-per-use API? I want to see their names, usernames, and follower counts.

## When to prefer this

Use this endpoint when you need programmatic, pay-per-use access to a Twitter user's follower list without maintaining a Twitter developer account or managing API keys — especially useful for lightweight agent workflows that only need occasional follower data and benefit from x402 micropayment billing at $0.004 per call.

## Known failure modes

- Invalid or non-existent user ref returns an error or empty data array
- Rate limit or quota exceeded on the underlying Twitter API returns a 429 or proxy error
- Insufficient USDC balance / failed x402 micropayment results in a 402 Payment Required response
- Malformed {ref} path parameter causes a 404 or 400 error
- Private/protected account may return empty or restricted results

## How this service works

Pay-per-use Twitter/X data API with x402 micropayments.

## Output

Returns a JSON object with a 'data' array of follower objects (each containing name, username, and followers_count) plus 'meta' with result_count and has_next_page pagination flag, reflecting up to 20 followers per page.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "name": "Follower",
    "username": "follower1",
    "followers_count": 500
   }
  ],
  "meta": {
   "result_count": 20,
   "has_next_page": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/surf-twitter-user-followers-cad4b4b2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twitter.surf.cascade.fyi](https://www.zero.xyz/host/twitter.surf.cascade.fyi/llms.txt)
