# Twitter Surf - User Followers

> Twitter Surf - 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-14).

Retrieves the list of followers for a specific Twitter/X user identified by their numeric user ID

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/users/867100084248469505/followers
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-surf-cascade-fyi-da803196
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EvztOQ0bsGKU3owRWiXmy

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 twitter-surf-cascade-fyi-da803196
```

Example prompt: Can you pull the list of followers for Twitter user ID 867100084248469505? If there are multiple pages, start from the beginning.

## When to prefer this

Use this endpoint when you need to programmatically retrieve the follower list for a known Twitter/X user by their numeric ID, especially in agentic workflows that require paginated traversal of a follower graph. Prefer this over scraping or direct Twitter API access when you need a pay-per-call model via x402 protocol without managing OAuth credentials yourself.

## Known failure modes

- Invalid or non-existent user ID returns an error or empty result
- Payment not included or insufficient USDC causes a 402 Payment Required response
- Rate limiting or quota exceeded on the underlying Twitter API
- Cursor value is invalid or expired, causing pagination to fail
- User account is private or suspended, resulting in restricted access

## How this service works

User followers

## Output

A paginated list of Twitter/X user accounts that follow the specified user, including profile data for each follower and a cursor for fetching the next page of results.

## 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"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "cursor": {
       "type": "string",
       "description": "Pagination cursor"
      }
     }
    }
   },
   "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/twitter-surf-cascade-fyi-da803196/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)
