# ReadX Tweet Edit History

> ReadX Tweet Edit History is a paid API for AI agents from readx.sh, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Retrieves the edit history of a specific tweet by username and tweet ID via X/Twitter JSON API, paid per call with USDC micropayments

## Facts

- Endpoint: GET https://readx.sh/api/%7Bname%7D/status/%7Bid%7D/history
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-tweet-edit-history-94d27432
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vgrn7c3LXIYltTiQT5Kf1

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-edit-history-94d27432
```

Example prompt: Can you pull the full edit history for the tweet with ID 1234567890123456789 posted by @elonmusk — I want to see what changes were made after it was first published?

## When to prefer this

Use this endpoint when you need to audit or verify the edit history of a specific tweet without managing Twitter API keys, and you prefer a pay-per-call USDC micropayment model over subscription-based API access. Ideal for fact-checking, journalism, research, or compliance workflows where tracking content changes on X/Twitter is required.

## Known failure modes

- Tweet not found — invalid tweet ID or deleted tweet returns error code
- Username not found — invalid or suspended account returns error
- Tweet was never edited — may return single-version history
- Payment failure — x402 micropayment not processed, request blocked
- Rate limiting — too many calls in a short period
- Tweet is private or from a protected account — access denied

## 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 response containing the edit history of the specified tweet, including all prior versions, edit timestamps, and content changes, keyed under a 'data' field with a status code.

## 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-edit-history-94d27432/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.sh](https://www.zero.xyz/host/readx.sh/llms.txt)
