# Surf Twitter - Tweet Replies

> Surf Twitter - Tweet Replies 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 replies to a specific tweet by its ID, returning reply text, author info, and pagination metadata.

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/tweets/%7Bid%7D/replies
- 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-tweet-replies-141e4ec7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_y9Ymcd1s8SkJcT3HF_Dan

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-tweet-replies-141e4ec7
```

Example prompt: Fetch all the replies to tweet ID 1234567890 on Twitter so I can see what people are saying in response to it.

## When to prefer this

Use this endpoint when you need to retrieve the reply thread for a specific tweet by ID and are comfortable with x402 micropayment billing at $0.004 USDC per call. Prefer over scraping when you need structured JSON output with author metadata and pagination support.

## Known failure modes

- Tweet ID not found or deleted — likely 404 or empty data array
- Tweet has no replies — returns empty data array with result_count 0
- Invalid tweet ID format — malformed request error
- Payment failure via x402 micropayment — 402 response blocking the call
- Rate limit exceeded — possible 429 response
- Private/protected tweet — access denied or empty result

## How this service works

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

## Output

Returns a JSON object with a `data` array of reply tweet objects (each with id, text, and author.username), plus a `meta` object containing result_count and has_next_page for pagination.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "id": "123",
    "text": "Reply text",
    "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-tweet-replies-141e4ec7/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)