# Twitter Tweet Replies Fetcher

> Twitter Tweet Replies Fetcher is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.04/call, status unknown (last checked 2026-09-14).

Fetches paginated replies to a specific tweet by its numeric ID, with cost-efficient pagination via parentRequestId chaining.

## Facts

- Endpoint: POST https://x402.orthogonal.com/fiber/v1/twitter/tweet-replies
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-tweet-replies-fetcher-460dc9dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oyPCTAPrVz227h5utO4vz

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 twitter-tweet-replies-fetcher-460dc9dc -d '<json body>'
```

Example prompt: Can you fetch all the replies to tweet ID 1812345678901234567 so I can see what people are saying about it?

## When to prefer this

Use this endpoint when you need to retrieve replies (comments) on a specific tweet and have its numeric tweet ID. Prefer this over keyword search endpoints when you already know the exact tweet and want its conversational thread. The pagination billing model (parentRequestId chaining) makes it economical for tweets with large reply volumes.

## Known failure modes

- Tweet ID not found or deleted — returns empty results or error
- Invalid or malformed tweet ID — validation error
- Cursor from a different logical search used — may return unexpected results or error
- Rate limiting or Twitter access restrictions — service unavailable response
- Non-pagination parameters changed while passing parentRequestId — treated as new billable request

## How this service works

Fetches paginated replies to a given tweet. Pagination billing: call the first page normally and save billing.requestId from the Orthogonal /v1/run response. For later page, offset, or cursor calls on the same logical search, pass parentRequestId with unchanged non-pagination parameters. Valid continuation calls still get their own request IDs and quoted price, but are charged 0. Changing filters starts a new billable request.

## Output

Returns a paginated list of tweet replies for the given tweet ID, including reply text, author metadata, engagement counts, and a cursor for fetching additional pages. The Orthogonal billing wrapper includes a requestId for chaining subsequent page calls at zero additional cost.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "cursor": {
   "type": "string",
   "description": "Pagination cursor. For later cursor pages of the same logical search, keep non-pagination parameters unchanged and pass top-level parentRequestId from the first Orthogonal /v1/run response."
  },
  "tweetId": {
   "type": "string",
   "description": "Numeric tweet ID."
  }
 }
}
```

## More

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