# SocialFetch Tweet Replies Lister

> SocialFetch Tweet Replies Lister is a paid API for AI agents from api.socialfetch.dev, paid per call via x402, $0.014/call, status unknown (last checked 2026-09-14).

Fetches and lists all replies to a specific tweet, given its URL or permalink.

## Facts

- Endpoint: GET https://api.socialfetch.dev/v1/twitter/tweets/replies
- Price: $0.014/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/socialfetch-tweet-replies-lister-6f8d2ccc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__0JYtquR9MSzpdj5TkuRr

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 socialfetch-tweet-replies-lister-6f8d2ccc
```

Example prompt: Can you pull all the replies to this tweet for me? https://twitter.com/elonmusk/status/1234567890

## When to prefer this

Use this endpoint when you need to retrieve the reply thread for a specific tweet by URL, especially for social listening, sentiment analysis, community research, or monitoring public reaction to a tweet. Prefer this over general Twitter search when you have a specific tweet permalink and want its direct replies rather than keyword-based results.

## Known failure modes

- Invalid or malformed tweet URL returns an error
- Tweet has been deleted or is private, resulting in not found error
- Rate limit exceeded returns a 429-like error
- Expired or invalid pagination cursor causes pagination failure
- Tweet exists but has zero replies, returning empty list

## How this service works

List replies to a tweet by URL.

## Output

A list of reply tweets to the specified tweet, including reply content, author details, timestamps, and engagement metrics, plus an opaque pagination cursor for retrieving additional replies in subsequent requests.

## 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",
     "required": [
      "url"
     ],
     "properties": {
      "url": {
       "type": "string",
       "maxLength": 4096,
       "minLength": 1,
       "description": "Tweet permalink or numeric id."
      },
      "cursor": {
       "type": "string",
       "minLength": 1,
       "description": "Opaque pagination cursor returned by a previous response."
      },
      "sortBy": {
       "enum": [
        "relevance",
        "recency",
        "likes"
       ],
       "type": "string",
       "description": "Reply sort order. Defaults to `relevance`."
      }
     }
    }
   },
   "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/socialfetch-tweet-replies-lister-6f8d2ccc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.socialfetch.dev](https://www.zero.xyz/host/api.socialfetch.dev/llms.txt)