# ReadX User Timeline

> ReadX User Timeline is a paid API for AI agents from x.1x402.sh, paid per call via x402, $0.03/call, status down (last checked 2026-09-16).

Fetches a user's X/Twitter timeline including their tweets, retweets, and quotes by username

## Facts

- Endpoint: GET https://x.1x402.sh/api/:name
- Price: $0.03/call
- Payment: x402
- Status: down
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-user-timeline-6df37eae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rtoYsm-En-kj-iq8uyLEd

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 readx-user-timeline-6df37eae
```

Example prompt: Can you pull the recent tweets, retweets, and quote tweets from @elonmusk's X/Twitter timeline for me?

## When to prefer this

Use this endpoint when you need a per-call, pay-as-you-go way to read a Twitter/X user's timeline without managing your own Twitter API credentials or subscriptions. Ideal for agents that need occasional timeline reads for arbitrary users without committing to a monthly API plan.

## Known failure modes

- Username not found — 404 or empty response if the account doesn't exist or has been suspended
- Private account — timeline may be inaccessible if the user has protected tweets
- Payment failure — 402 response if USDC payment via x402 protocol is not completed
- Rate limiting — too many requests in a short period may result in throttling
- Username typo — incorrect casing or misspelling returns no results

## How this service works

A user's timeline: tweets, retweets and quotes. Example: GET /api/jack

## Output

Returns a JSON array of the user's recent timeline entries including original tweets, retweets, and quote tweets — with tweet text, timestamps, engagement counts, and metadata for each post.

## 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"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_]+$",
       "minLength": 1,
       "description": "X handle without the leading @ (alphanumeric and underscore)."
      },
      "cursor": {
       "type": "string",
       "description": "Pagination cursor from a previous response's pagination.bottom (or replies.bottom)."
      }
     }
    }
   },
   "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/readx-user-timeline-6df37eae/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x.1x402.sh](https://www.zero.xyz/host/x.1x402.sh/llms.txt)