# ReadX — Tweet Status History

> ReadX — Tweet Status History 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-16).

Retrieves the edit/version history of a specific tweet by username and tweet ID via X/Twitter API with x402 micropayment

## Facts

- Endpoint: GET https://readx.1x402.sh/api/%7Bname%7D/status/%7Bid%7D/history
- Price: $0.05/call
- Payment: x402
- Status: down
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-tweet-status-history-8eb0862c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f4i0YAaOn8WnvMNekzuQy

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-tweet-status-history-8eb0862c
```

Example prompt: Can you pull the full edit history for @elonmusk's tweet with ID 1234567890123456789 — I want to see all the versions of that tweet since it was first posted.

## When to prefer this

Use this endpoint when you need to retrieve the edit/version history of a specific tweet and know both the Twitter username and tweet ID. Prefer this over general tweet lookup endpoints when the goal is specifically to track changes or edits to a tweet over time. Best suited for fact-checking, journalism, or research workflows where tweet mutation matters. Requires no X/Twitter API key — only a one-time $0.05 USDC micropayment via x402.

## Known failure modes

- Tweet ID not found — returns error code with empty data
- Username not found or incorrect — lookup fails
- Tweet has no edit history (was not edited) — returns single version or empty history
- Payment failure via x402 — request blocked without valid USDC micropayment
- Rate limiting or upstream X/Twitter API unavailability — returns error response
- Invalid username or ID format in URL path — malformed request error

## How this service works

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

## Output

A JSON object containing the historical versions or edit states of the specified tweet, including metadata about each version, returned as structured data with a status code and data payload.

## 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-tweet-status-history-8eb0862c/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)
