# ReadX Tweet Replies API

> ReadX Tweet Replies API is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Fetches paginated replies to a specific tweet by numeric tweet ID using the ReadX X/Twitter API

## Facts

- Endpoint: GET https://readx.sh/api/tweets/:id/replies
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-tweet-replies-api-304677fe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H1F7lTXzKklSX_rhgMRZR

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 readx-tweet-replies-api-304677fe
```

Example prompt: Can you pull all the replies to tweet ID 1234567890 using ReadX? Paginate through all of them until there are no more results.

## When to prefer this

Use this endpoint when you need to retrieve the replies/comments for a specific tweet and have the tweet's numeric ID. It supports cursor-based pagination for tweets with many replies. Prefer this over search-based approaches when you already know the exact tweet ID and want a complete, ordered list of its direct replies.

## Known failure modes

- Invalid tweet ID format (must be numeric, up to 19 digits) returns a 400 error
- Tweet not found or deleted returns a 404 error
- No replies exist for the tweet returns an empty list
- Invalid or expired cursor returns a pagination error
- Rate limiting or payment failure returns a 402 error
- Tweet is from a private/protected account and inaccessible

## How this service works

Replies to a tweet (paginate with cursor until has_more is false). Example: GET /api/tweets/20/replies

## Output

Returns a paginated list of reply tweets for the given tweet ID, including tweet content, author metadata, engagement metrics, and a pagination cursor to fetch the next page of replies. The has_more field indicates whether additional pages exist.

## 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",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "pattern": "^[0-9]{1,19}$",
       "description": "Numeric tweet id (up to 19 digits)."
      },
      "cursor": {
       "type": "string",
       "description": "Pagination cursor from a previous response's pagination.next_cursor (the conversation endpoint at /api/{name}/tweets/{id} instead takes its own nested reply cursor — see that endpoint)."
      }
     }
    }
   },
   "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/readx-tweet-replies-api-304677fe/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.sh](https://www.zero.xyz/host/readx.sh/llms.txt)