# Surf Twitter – Verified Followers

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

Returns a paginated list of verified (blue-checkmark) followers for a given Twitter/X user, paid via x402 micropayment.

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/users/%7Bref%7D/verified_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-verified-followers-cb6364c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uLPQTe0yJOsfSEky9HDbL

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-verified-followers-cb6364c1
```

Example prompt: Can you pull the list of verified (blue-checkmark) followers for the Twitter account @nytimes using the Surf Twitter API?

## When to prefer this

Use this endpoint when you need specifically the verified (blue-checkmark) subset of a Twitter/X user's followers, and want pay-per-call pricing via x402 micropayments rather than a subscription. Ideal for lightweight, one-off lookups or when you want to audit the credibility profile of an account's audience without paying for full follower data.

## Known failure modes

- Invalid or non-existent user reference returns 404 or empty data array
- Insufficient USDC balance / failed x402 micropayment returns 402 Payment Required
- Rate limiting or quota exceeded returns 429
- Private/suspended account returns 403 or empty result
- Malformed {ref} path parameter causes 400 Bad Request

## How this service works

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

## Output

A JSON object containing an array of verified follower objects (each with name, username, and is_blue_verified=true) plus pagination metadata including result_count and has_next_page, allowing the agent to iterate through all pages.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "name": "Verified User",
    "username": "verified1",
    "is_blue_verified": true
   }
  ],
  "meta": {
   "result_count": 10,
   "has_next_page": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/surf-twitter-verified-followers-cb6364c1/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)