# Surf Twitter – List Tweets

> Surf Twitter – List Tweets 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-16).

Fetches tweets from a specified Twitter/X list by list ID, using x402 micropayments.

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/lists/%7Bid%7D/tweets
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/surf-twitter-list-tweets-5bed66e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_NdRNLZYpe1ysfHCJoL_IK

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-list-tweets-5bed66e1
```

Example prompt: Can you pull the latest tweets from Twitter list ID 1234567890 for me?

## When to prefer this

Use this endpoint when you need tweet content from a specific Twitter/X list identified by its list ID and are operating in an x402 micropayment context. Prefer this over scraping or other Twitter APIs when you want pay-per-use access without managing OAuth tokens or monthly API subscriptions.

## Known failure modes

- Invalid or non-existent list ID returns an empty data array or 404-equivalent error
- Private or restricted lists may return an authorization error
- Payment failure via x402 results in a 402 Payment Required response before data is returned
- Malformed list ID (non-string or empty) triggers a 400 Bad Request validation error
- Rate limiting or upstream Twitter API errors may cause intermittent 5xx failures

## How this service works

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

## Output

A JSON object containing an array of tweets from the specified list, each with a tweet ID, text, and author username, plus metadata including result count and a boolean indicating whether more pages are available.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "id": "123",
    "text": "List tweet",
    "author": {
     "username": "user1"
    }
   }
  ],
  "meta": {
   "result_count": 20,
   "has_next_page": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/surf-twitter-list-tweets-5bed66e1/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)