# ReadX Single Tweet Lookup

> ReadX Single Tweet Lookup 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).

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

## Facts

- Endpoint: GET https://readx.sh/api/status/:id
- 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-single-tweet-lookup-08fc0c5d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8PlrQBP8ZsWIjlXG06TQJ

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-08fc0c5d
```

Example prompt: Can you pull up the tweet with ID 1234567890123456789 from X and show me what it says, including who posted it and any engagement stats?

## When to prefer this

Use this endpoint when you have a specific numeric tweet ID and need its standalone content and metadata quickly, without needing thread context or conversation replies. Prefer this over search endpoints when you already know the exact tweet ID. Ideal for agents verifying tweet content, archiving specific posts, or enriching data pipelines with tweet details.

## Known failure modes

- Tweet ID not found or deleted — likely returns 404 or empty result
- Invalid tweet ID format (non-numeric or too long) — rejected by schema validation
- Tweet from a private/suspended account — may return error or empty data
- Payment failure via x402 — endpoint returns 402 before serving data
- Rate limiting — too many requests in a short window

## How this service works

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

## Output

A JSON object representing the single tweet: tweet text, author details, timestamps, engagement counts (likes, retweets), and other tweet metadata — without any surrounding replies or 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-08fc0c5d/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)