# glim.sh Twitter Fetch Tweet by ID

> glim.sh Twitter Fetch Tweet by ID is a paid API for AI agents from glim.sh, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Fetches a single tweet's data from Twitter/X by its tweet ID

## Facts

- Endpoint: POST https://glim.sh/api/v1/twitter/tweets/:id
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-twitter-fetch-tweet-by-id-eb7cc144
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kjJqJM8wJ2g_wZDml1lxq

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 glim-sh-twitter-fetch-tweet-by-id-eb7cc144 -d '<json body>'
```

Example prompt: Pull the full details of this tweet for me — tweet ID 1234567890123456789 — I want the text, author, and engagement stats.

## When to prefer this

Use this endpoint when you have a specific tweet ID and need full tweet details including text, author, and engagement data. Prefer this over list/search endpoints when you already know the exact tweet you need. Ideal for verifying tweet content, enriching datasets with tweet metadata, or following up on a known tweet reference.

## Known failure modes

- Tweet not found — tweet ID does not exist or was deleted
- Invalid tweet ID format — non-numeric or malformed ID provided
- Tweet from private/suspended account — access restricted
- Payment failure — x402 payment of $0.001 USDC not processed
- Rate limiting — too many requests in a short period
- API timeout — Twitter upstream unavailability

## How this service works

Fetch a tweet by ID

## Output

Returns tweet data including tweet text/content, author information, posting timestamp, and engagement metrics (likes, retweets, replies) for the specified tweet ID.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "properties": {},
     "description": "No body parameters - the tweet id is taken from the URL path"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "data"
     ],
     "properties": {
      "data": {
       "type": "object",
       "propertyNames": {
        "type": "string"
       },
       "additionalProperties": {}
      }
     }
    }
   }
  }
 }
}
```

## More

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