# X Tweet Lookup by ID

> X Tweet Lookup by ID is a paid API for AI agents from agent402.tools, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-23).

Fetches a single public X (Twitter) tweet by numeric ID, returning full text, engagement metrics, author details, and metadata.

## Facts

- Endpoint: POST https://agent402.tools/api/x-tweet?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x-tweet-lookup-by-id-c579065c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Jmer5mme2DuUFcSC-g1rf

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 x-tweet-lookup-by-id-c579065c -d '<json body>'
```

Example prompt: Can you pull up the details for tweet ID 1800000000000000000 — I want to see the full text, who posted it, and how many likes, retweets, and impressions it got?

## When to prefer this

Use this endpoint when you have a specific tweet ID or status URL and need structured data about that single tweet — especially engagement metrics and author details — without building your own X API integration or managing OAuth credentials. Ideal for agents that need pay-per-call access to tweet data without a subscription.

## Known failure modes

- Tweet not found or deleted — no tweet object returned
- Invalid or malformed tweet ID — likely a 400 or error response
- Tweet from a private/protected account — data unavailable
- Rate limiting or upstream X API quota exceeded — request fails
- Network timeout reaching X API v2 — transient error

## How this service works

Fetch one public tweet on X (Twitter) by id: text, created time, language, conversation id, engagement metrics (likes, retweets, replies, quotes, bookmarks, impressions) and the author's username, name and verification.

## Output

Returns a JSON object with the tweet's ID, full text, URL, language code, created timestamp, conversation ID, sensitivity flag, author (name, username, verified status, author ID), and engagement metrics (likes, retweets, replies, quotes, bookmarks, impressions), plus a source tag and fetch timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "id": {
   "type": "string",
   "description": "Numeric tweet id (the trailing number of a status URL)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "tweet": {
   "id": "20",
   "url": "https://x.com/jack/status/20",
   "lang": "en",
   "text": "just setting up my twttr",
   "author": {
    "name": "jack",
    "username": "jack",
    "verified": false
   },
   "metrics": {
    "likes": 180000,
    "quotes": 30000,
    "replies": 10000,
    "retweets": 120000,
    "bookmarks": 5000,
    "impressions": 0
   },
   "authorId": "12",
   "createdAt": "2006-03-21T20:50:14.000Z",
   "conversationId": "20",
   "possiblySensitive": false
  },
  "source": "x-api-v2",
  "fetchedAt": "2026-08-20T14:10:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x-tweet-lookup-by-id-c579065c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent402.tools](https://www.zero.xyz/host/agent402.tools/llms.txt)