# 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 tweet ID, returning reply text, author, and engagement metadata

## Facts

- Endpoint: GET https://readx.sh/api/tweets/%7Bid%7D/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-054c2ced
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OjRgmYFYC6tnbqT5xzPlV

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-054c2ced
```

Example prompt: Can you pull all the replies to tweet ID 1234567890 on X/Twitter and show me what people are saying?

## When to prefer this

Use this endpoint when you need to retrieve replies to a specific tweet by ID without setting up X/Twitter API credentials, and are comfortable paying $0.03 USDC per call via x402 micropayments on Base or Solana. Ideal for agents that need on-demand reply data without OAuth setup overhead, or for lightweight use cases where a full Twitter API subscription is overkill.

## Known failure modes

- Tweet ID not found or deleted — empty tweets array or 404 error
- Invalid tweet ID format — malformed request error
- Tweet has no replies — empty tweets array returned
- Payment failure via x402 — 402 Payment Required before data is returned
- Rate limiting or upstream X API unavailability — 5xx error
- Cursor invalid or expired — pagination resets or error returned

## How this service works

ReadX is a read-only X/Twitter JSON API. Profiles, timelines, tweets, search, lists, followers &amp; following — pay per call with x402 micropayments in USDC on Base or Solana. No API keys.

## Output

Returns a JSON object containing an array of reply tweets, each with tweet ID, text content, author username, creation timestamp, and like count, plus a has_more boolean and next_cursor string for paginating through additional replies.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 0,
  "data": {
   "tweets": [
    {
     "id": "21",
     "card": null,
     "isAI": false,
     "isAd": false,
     "note": null,
     "poll": null,
     "text": "great point",
     "time": 1142974214,
     "user": {
      "id": "99",
      "bio": "",
      "likes": 0,
      "media": 0,
      "banner": "",
      "tweets": 30000,
      "userPic": "",
      "website": "",
      "fullname": "Someone",
      "joinDate": 1142974214,
      "location": "",
      "username": "someone",
      "followers": 599,
      "following": 307,
      "protected": false,
      "suspended": false,
      "pinnedTweet": "0",
      "verifiedType": "Blue"
     },
     "media": null,
     "quote": null,
     "reply": [],
     "stats": {
      "likes": 3,
      "views": 0,
      "quotes": 0,
      "replies": 0,
      "retweets": 0
     },
     "pinned": false,
     "source": "",
     "history": null,
     "replyId": "0",
     "retweet": null,
     "location": "",
     "threadId": "20",
     "available": true,
     "hasThread": false,
     "mediaTags": null,
     "tombstone": "",
     "attribution": null
    }
   ]
  },
  "pagination": {
   "has_more": true,
   "next_cursor": "DAABCgABG...cursor"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-tweet-replies-api-054c2ced/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)
