# Twitter/X User Timeline Fetcher

> Twitter/X User Timeline Fetcher is a paid API for AI agents from twit-api-production-de12.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-09, last successful call 2026-07-15).

Fetches recent tweets from a specific Twitter/X user account by screen name, with pagination support.

## Facts

- Endpoint: GET https://twit-api-production-de12.up.railway.app/tweets/user?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-09
- Last successful call: 2026-07-15
- Success rate: 100% of calls made through Zero
- Rating: 4.3 / 5 from 2 reviews
- Activations on Zero: 17
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-x-user-timeline-fetcher-f57bea2c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AVtAHm-D_8XUwRiRyeO8P

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-x-user-timeline-fetcher-f57bea2c
```

Example prompt: Can you fetch the latest tweets from the Twitter account @elonmusk so I can see what he's been posting recently?

## When to prefer this

Use this endpoint when you need to retrieve tweets from a specific known Twitter user by their screen name, especially for timeline monitoring, user research, or content aggregation. Prefer this over the search endpoint when you already know the exact account and want their personal tweet history rather than topic-based results.

## Known failure modes

- Username not found or account suspended — returns error indicating user does not exist
- Rate limit exceeded — returns 429-like error after too many requests
- Invalid or expired next_token — pagination cursor rejected
- Private/protected account — tweets not accessible without follow approval
- Payment not fulfilled — x402 payment required before response is returned

## How this service works

Fetches tweets from a specific user account.

## Output

Returns a list of up to 20 recent tweets from the specified user, most recent first, along with a next_token cursor for paginating through older tweets. Each tweet includes the tweet text and associated metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "username"
     ],
     "properties": {
      "username": {
       "type": "string",
       "description": "Twitter screen name (without @)"
      },
      "next_token": {
       "type": "string",
       "description": "Pagination cursor from previous response"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/twitter-x-user-timeline-fetcher-f57bea2c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twit-api-production-de12.up.railway.app](https://www.zero.xyz/host/twit-api-production-de12.up.railway.app/llms.txt)