# X Data Gateway – Tweet Replies

> X Data Gateway – Tweet Replies is a paid API for AI agents from x-data-gateway.annushka1190.workers.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-09-13).

Fetches replies to a specific tweet by its numeric ID from the Twitter/X platform in real-time

## Facts

- Endpoint: GET https://x-data-gateway.annushka1190.workers.dev/tweets/replies
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x-data-gateway-tweet-replies-327976f9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pbFImekQO1hi7IZftNC-6

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 x-data-gateway-tweet-replies-327976f9
```

Example prompt: Pull all the replies to tweet ID 1874392810234567890 and show me what people are saying in response to it.

## When to prefer this

Choose this endpoint when you need real-time reply data for a specific tweet without setting up a Twitter Developer account or managing API keys. Ideal for AI agents that need pay-per-request access to Twitter conversation threads using USDC micropayments via x402. Prefer over direct Twitter API when you want zero-setup access or are operating in a headless/agent environment.

## Known failure modes

- Invalid or non-numeric tweet ID returns an error
- Tweet has no replies returns an empty data array
- Tweet is from a private/protected account returns forbidden or empty response
- Payment failure via x402 returns 402 Payment Required
- Rate limits on the underlying Twitter API may cause upstream errors
- Deleted or unavailable tweet returns not found error

## How this service works

Replies to a post by numeric ID. e.g. GET /tweets/replies?id=20

## Output

Returns a JSON array of reply tweet objects, each containing a tweet ID and reply text, along with pagination metadata including a next_token for retrieving additional pages of replies.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "description": "Parent tweet ID"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x-data-gateway-tweet-replies-327976f9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x-data-gateway.annushka1190.workers.dev](https://www.zero.xyz/host/x-data-gateway.annushka1190.workers.dev/llms.txt)