# twit.sh Tweet Lookup by ID

> twit.sh Tweet Lookup by ID is a paid API for AI agents from twit.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Fetches real-time tweet data (text, author, engagement metrics) for up to 50 tweets by their numeric IDs, paid per-request via USDC on Base.

## Facts

- Endpoint: GET https://twit.sh/tweets
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twit-sh-tweet-lookup-by-id-5331ee5e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_d6TNyRI2kPN-EpOeRT9qs

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 twit-sh-tweet-lookup-by-id-5331ee5e
```

Example prompt: Can you pull up the full details — text, author, and engagement stats — for these tweet IDs: 1110302988 and 1234567890?

## When to prefer this

Choose this endpoint when you already have specific tweet IDs and need to hydrate them into full tweet objects with engagement metrics, without requiring OAuth credentials or API key setup. Ideal for autonomous agents needing pay-per-use, no-registration access to Twitter/X data at $0.01 per call via x402/USDC on Base.

## Known failure modes

- Invalid or non-numeric tweet IDs return an error or empty data array
- More than 50 IDs in a single request may be rejected or truncated
- Deleted or suspended tweets return no data for that ID
- Payment failure (insufficient USDC on Base) blocks the request entirely
- Tweets from private/protected accounts may not be accessible

## How this service works

Real-time Twitter/X data for AI agents. No sign-up, no API keys. Pay per request in USDC on Base via x402. Fully autonomous.

## Output

Returns a JSON array of tweet objects, each containing the tweet's numeric ID, full text, author object (id, name, username), ISO 8601 created_at timestamp, and public_metrics (like_count, quote_count, reply_count, retweet_count). Up to 50 tweets per call.

## 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"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "ids"
     ],
     "properties": {
      "ids": {
       "type": "string",
       "description": "Comma-separated numeric tweet IDs, max 50"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": [
   {
    "id": "1110302988",
    "text": "Running bitcoin",
    "author": {
     "id": "9253672",
     "name": "Hal Finney",
     "username": "halfin"
    },
    "created_at": "2009-01-11T03:39:18.000Z",
    "public_metrics": {
     "like_count": 134000,
     "quote_count": 3500,
     "reply_count": 5400,
     "retweet_count": 32000
    }
   }
  ]
 }
}
```

## More

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