# Fiber AI Tweet Replies

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

Fetches paginated replies to a given tweet on Twitter/X.

## Facts

- Endpoint: POST https://mpp.orthogonal.com/fiber/v1/twitter/tweet-replies
- Price: $0.04/call
- Payment: MPP
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Provider: Fiber AI API
- Docs: https://api.fiber.ai
- Website: https://api.fiber.ai
- Tags: contacts, email, phone, enrichment, data
- Canonical page: https://www.zero.xyz/c/fiber-ai-api-fiber-ai-tweet-replies-8c27324d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m581bUlySfjD0qDpxgg-s

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 fiber-ai-api-fiber-ai-tweet-replies-8c27324d -d '<json body>'
```

Example prompt: Can you fetch me the first page of replies to this tweet — tweet ID 1801234567890123456 — so I can see what people are saying about it?

## When to prefer this

Use this endpoint when you need to retrieve public reply threads for a specific tweet, especially for downstream tasks like sentiment analysis, community feedback collection, or social listening. Prefer this over direct Twitter API access when you want a simple, paginated, cost-effective interface without managing OAuth credentials.

## Known failure modes

- Tweet ID not found or tweet deleted — returns 404 or empty result
- Rate limit exceeded — returns 429 error
- Invalid or malformed tweet ID — returns 400 bad request
- Tweet has no replies — returns empty list
- Pagination cursor expired or invalid — returns error or resets to first page
- Network timeout on Fiber AI backend — returns 503

## 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

A paginated list of reply tweets for the specified tweet, including reply text, author information, timestamps, and a cursor for fetching subsequent pages (up to some number of replies per page).

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fiber-ai-api-fiber-ai-tweet-replies-8c27324d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mpp.orthogonal.com](https://www.zero.xyz/host/mpp.orthogonal.com/llms.txt)
