# glim.sh Twitter Tweet Replies Fetcher

> glim.sh Twitter Tweet Replies Fetcher is a paid API for AI agents from glim.sh, paid per call via x402, $0.004/call, status unknown (last checked 2026-09-08).

Fetches replies to a specific tweet by its ID, returning recent reply tweets with their content and metadata

## Facts

- Endpoint: POST https://glim.sh/api/v1/twitter/tweets/%7Bid%7D/replies
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-08
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-twitter-tweet-replies-fetcher-d2257958
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-H_EnA3-Lspn9aUE52Arl

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 glim-sh-twitter-tweet-replies-fetcher-d2257958 -d '<json body>'
```

Example prompt: Can you pull the replies to tweet ID 1234567890 — I want to see up to 30 responses to that post?

## When to prefer this

Use this endpoint when you need live reply data for a specific tweet without managing your own Twitter API credentials or scraping infrastructure. Ideal for agents that need to analyze tweet conversations, monitor public reactions to a post, or extract discussion threads on demand with per-call micropayment pricing.

## Known failure modes

- Tweet ID not found or deleted — empty data array or 404-equivalent response
- Tweet has no replies — returns empty data array with result_count of 0
- Invalid tweet ID format — may return error or empty result
- Rate limit or payment failure — 402 payment required or throttling error
- Private or suspended account tweet — access denied or empty result

## How this service works

One remote endpoint gives your agent live data from Twitter, Reddit, the open web, GitHub and more. No API keys, no scraping stack - just connect the URL and go.

## Output

A JSON object containing an array of reply tweets (each with tweet ID and text), plus metadata including the total result count returned for the queried tweet.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "POST"
     ]
    },
    "bodyType": {
     "type": "string",
     "enum": [
      "json",
      "form-data",
      "text"
     ]
    },
    "body": {
     "type": "object",
     "properties": {
      "sort": {
       "default": "Relevance",
       "description": "Reply sort",
       "type": "string",
       "enum": [
        "Relevance",
        "Latest",
        "Likes"
       ]
      },
      "cursor": {
       "description": "Pagination cursor",
       "type": "string"
      },
      "since": {
       "description": "Only include replies after this Unix timestamp",
       "type": "integer",
       "minimum": -9007199254740991,
       "maximum": 9007199254740991
      },
      "until": {
       "description": "Only include replies before this Unix timestamp",
       "type": "integer",
       "minimum": -9007199254740991,
       "maximum": 9007199254740991
      }
     }
    },
    "pathParams": {
     "type": "object"
    }
   },
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "data": {
       "type": "array",
       "items": {
        "type": "object",
        "propertyNames": {
         "type": "string"
        },
        "additionalProperties": {}
       }
      },
      "meta": {
       "type": "object",
       "properties": {
        "result_count": {
         "type": "integer",
         "minimum": -9007199254740991,
         "maximum": 9007199254740991
        },
        "has_next_page": {
         "type": "boolean"
        },
        "next_cursor": {
         "type": "string"
        }
       },
       "required": [
        "result_count"
       ]
      },
      "summary": {
       "type": "object",
       "propertyNames": {
        "type": "string"
       },
       "additionalProperties": {}
      }
     },
     "required": [
      "data",
      "meta"
     ]
    }
   },
   "required": [
    "type"
   ]
  }
 },
 "required": [
  "input"
 ]
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "id": "1234567890",
    "text": "Example tweet"
   }
  ],
  "meta": {
   "result_count": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/glim-sh-twitter-tweet-replies-fetcher-d2257958/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from glim.sh](https://www.zero.xyz/host/glim.sh/llms.txt)