# Twitter Surf - Tweet Replies

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

Fetches replies to a specific tweet, sortable by relevance, latest, or likes, with pagination support

## Facts

- Endpoint: GET https://twitter.surf.cascade.fyi/tweets/2049411678094479474/replies
- 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-173c2c55
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KySq3GMXhLz3ZB7_EJQPj

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-173c2c55
```

Example prompt: Show me the most liked replies to tweet ID 2049411678094479474 — fetch them sorted by Likes.

## When to prefer this

Use this endpoint when you need to retrieve replies to a specific tweet by ID and want control over sort order (Relevance, Latest, Likes) and pagination. Ideal for agents monitoring tweet engagement, analyzing discourse around a tweet, or collecting threaded responses. Prefer this over scraping Twitter directly given its pay-per-call model via x402 and structured response.

## Known failure modes

- Tweet ID does not exist or has been deleted — empty or error response
- Tweet has no replies — empty results list
- Invalid sort enum value — request rejected or ignored
- Expired or invalid pagination cursor — may return duplicate or unexpected results
- Rate limiting or payment failure — HTTP 402 or 429 response
- Private or protected tweet — replies may not be accessible

## How this service works

Tweet replies

## Output

A paginated list of reply tweets for the specified tweet ID, including tweet content, author info, and engagement data. Response can be sorted by Relevance, Latest, or Likes, and includes a cursor for fetching subsequent pages. The raw response payload can be quite large (166KB+).

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {
   "sort": "Likes"
  }
 }
}
```

## 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"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "sort": {
       "enum": [
        "Relevance",
        "Latest",
        "Likes"
       ],
       "type": "string"
      },
      "cursor": {
       "type": "string",
       "description": "Pagination cursor"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "_truncated",
  "_originalSize"
 ],
 "properties": {
  "_truncated": {
   "type": "boolean"
  },
  "_originalSize": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/twitter-surf-cascade-fyi-173c2c55/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)