# Twitter Tweet Retweeters Lookup

> Twitter Tweet Retweeters Lookup 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 a paginated list of users who retweeted a specific tweet, with cost-efficient pagination via request ID chaining.

## Facts

- Endpoint: POST https://x402.orthogonal.com/fiber/v1/twitter/tweet-retweeters
- 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-retweeters-lookup-68796454
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XqwrnKBXe7BzfQlus0949

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-retweeters-lookup-68796454 -d '<json body>'
```

Example prompt: Can you get me the list of users who retweeted tweet ID 1234567890? Fetch the first page and if there are more, continue paginating using the request ID from the first response.

## When to prefer this

Use this endpoint when you need to enumerate the users who retweeted a specific tweet, especially across multiple pages. The built-in pagination billing model (using parentRequestId) makes it cost-efficient for large retweet lists — only the first page is charged. Prefer this over building your own Twitter API integration when you need quick, pay-per-use access without managing OAuth credentials.

## Known failure modes

- Invalid or non-existent tweet ID returns an error or empty result
- Tweet is from a protected/private account and retweeters are not accessible
- Pagination cursor mismatch or expiration causes failed continuation
- Changing non-pagination parameters with a parentRequestId starts a new billable request unexpectedly
- Rate limiting or upstream Twitter API unavailability causes request failure

## How this service works

Fetches paginated list of users who retweeted a 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 Twitter user objects who retweeted the specified tweet, along with a pagination cursor for fetching subsequent pages and a billing requestId for cost-free continuation calls on the same logical search.

## 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-retweeters-lookup-68796454/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)