# ReadX Single Tweet Lookup

> ReadX Single Tweet Lookup is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-16).

Fetches the JSON data for a single tweet by its numeric ID, without surrounding conversation context

## Facts

- Endpoint: GET https://readx.sh/api/tweets/:id
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-single-tweet-lookup-64a14e7a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9otpLUosxx7n75mlH9qZH

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-single-tweet-lookup-64a14e7a
```

Example prompt: Can you pull the tweet with ID 1234567890123456789 from ReadX and show me what it says?

## When to prefer this

Use this endpoint when you need the raw JSON data for a single known tweet by its numeric ID and do not need the surrounding thread or conversation context. Prefer this over scraping or the official X API when you want a simple pay-per-call model without OAuth setup.

## Known failure modes

- Invalid tweet ID format (non-numeric or more than 19 digits) returns a validation error
- Tweet not found or deleted returns a 404 or empty result
- Tweet ID belongs to a private/suspended account may return no data
- Payment of 0.03 USDC not fulfilled returns a 402 Payment Required
- Rate limiting or upstream X API unavailability returns a 5xx error

## How this service works

A single tweet on its own, without the surrounding conversation. Example: GET /api/tweets/20

## Output

A JSON object containing the tweet's content and metadata — such as text, author, timestamp, engagement counts, and related fields — for the single specified tweet, without any surrounding conversation thread.

## 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": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "pattern": "^[0-9]{1,19}$",
       "description": "Numeric tweet id (up to 19 digits)."
      }
     }
    }
   },
   "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-single-tweet-lookup-64a14e7a/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)