# ReadX — X/Twitter User Media Timeline API

> ReadX — X/Twitter User Media Timeline API is a paid API for AI agents from readx.1x402.sh, paid per call via x402, $0.05/call, status down (last checked 2026-09-15).

Fetches the media timeline (photos, videos, GIFs) posted by a specific X/Twitter user, returning JSON results via x402 micropayment.

## Facts

- Endpoint: GET https://readx.1x402.sh/api/%7Bname%7D/media
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-x-twitter-user-media-timeline-api-319e9cc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GEELTeCfxKqO-LgRt83Oi

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-x-twitter-user-media-timeline-api-319e9cc0
```

Example prompt: Can you pull all the recent photos and videos that @elonmusk has posted on X/Twitter and show me the media URLs?

## When to prefer this

Use this endpoint when you need to retrieve the media (images, videos, GIFs) posted by a specific X/Twitter user without setting up X API keys — ideal for agents that need lightweight, pay-per-call access to a user's visual tweet history using USDC micropayments on Base or Solana.

## Known failure modes

- Unknown or suspended X username returns empty data or error code
- Payment not completed causes 402 response and no data returned
- Rate limits on the underlying X API cause delayed or failed responses
- Private/protected accounts return no media data
- Malformed username path parameter causes 4xx error

## How this service works

ReadX is a read-only X/Twitter JSON API. Profiles, timelines, tweets, search, lists, followers & following — pay per call with x402 micropayments in USDC on Base or Solana. No API keys.

## Output

A JSON object with a code field (0 on success) and a data payload containing the user's media timeline — tweets that include photos, videos, or GIFs — along with associated metadata such as tweet IDs, timestamps, and direct media URLs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 0,
  "data": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-x-twitter-user-media-timeline-api-319e9cc0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.1x402.sh](https://www.zero.xyz/host/readx.1x402.sh/llms.txt)