# Orthogonal Twitter/X User Tweets Fetcher

> Orthogonal Twitter/X User Tweets 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 tweets from a specified Twitter/X user handle, with cost-efficient pagination via parent request ID chaining.

## Facts

- Endpoint: POST https://x402.orthogonal.com/fiber/v1/twitter/user-tweets
- 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/orthogonal-twitter-x-user-tweets-fetcher-ff5c2b55
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qJTyFEZZTEU3FZv29pbL8

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 orthogonal-twitter-x-user-tweets-fetcher-ff5c2b55 -d '<json body>'
```

Example prompt: Can you fetch the recent tweets from @elonmusk's Twitter account and show me his latest posts?

## When to prefer this

Choose this endpoint when you need to retrieve tweets from a specific known Twitter/X user by handle, especially when you need to paginate through multiple pages of results cost-efficiently using the parentRequestId chaining mechanism. Prefer this over generic search endpoints when you know exactly whose tweets you want rather than searching by keyword or topic.

## Known failure modes

- Invalid or non-existent Twitter handle returns an error or empty result
- Expired or invalid cursor causes pagination failure
- Rate limiting or access restrictions on the target account (private accounts)
- Missing required 'handle' parameter results in a validation error
- Changing non-pagination parameters while passing parentRequestId triggers a new billable request

## How this service works

Fetches paginated tweets from a Twitter/X user. 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 tweets from the specified Twitter/X user, including tweet content and metadata, along with a pagination cursor for subsequent pages and a billing requestId that can be used as parentRequestId for cost-free continuation calls on the same logical query.

## 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."
  },
  "handle": {
   "type": "string",
   "description": "Twitter/X handle."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orthogonal-twitter-x-user-tweets-fetcher-ff5c2b55/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)