Look up any tweet by numeric ID via x402 — pay $0.0025 USDC per request on Base.
What it does
The `/tweets/by/id` endpoint on twit.sh returns full details of a single Twitter/X post given its numeric tweet ID. The response follows the X v2 API-compatible JSON format and includes the tweet's full text, author information, and engagement metrics. Payment is handled inline via the x402 protocol: the server returns a 402 challenge with a USDC payment request on Base mainnet, the caller settles and retries with a payment proof header, and the data comes back in a single round-trip. No API key, OAuth flow, or account creation is required.
This endpoint is part of the broader twit.sh API, which covers user lookups, tweet search, timelines, followers/following, lists, communities, articles, and authenticated actions (post, like, retweet, bookmark). The `/tweets/by/id` endpoint is one of the cheapest at $0.0025 USDC per call. The data is described as sourced from the open web and shaped into clean JSON. All pagination-capable sibling endpoints support cursor-based pagination.
twit.sh is designed for autonomous AI agents. It ships as an npm CLI skill (`npx twitsh`) compatible with Claude Code, Cursor, OpenClaw, Hermes, Codex, and similar agent frameworks. The skill handles wallet setup, payment, and credential injection automatically.
Capabilities
Use cases
- —Retrieve full text and engagement metrics for a specific tweet by its numeric ID
- —Feed tweet content into an AI agent pipeline for sentiment analysis or summarization
- —Monitor specific tweets for engagement changes over time
- —Verify tweet existence and content programmatically without X API credentials
- —Enrich datasets with tweet metadata for research or analytics
Fit
Best for
- —AI agents that need on-demand tweet data without OAuth setup
- —Developers who want pay-per-request Twitter data without monthly subscriptions
- —Crypto-native applications settling micropayments in USDC on Base
Not for
- —High-volume bulk tweet ingestion (pay-per-call adds up; official firehose may be cheaper at scale)
- —Authenticated write actions on this specific endpoint (use sibling /tweets POST for that)
Quick start
curl -X GET 'https://x402.twit.sh/tweets/by/id?id=1110302988'
# Returns 402 with payment challenge.
# After settling USDC on Base, retry with proof:
curl -X GET 'https://x402.twit.sh/tweets/by/id?id=1110302988' \
-H 'X-PAYMENT: <payment_proof>'Example
Response
{
"data": {
"id": "1110302988",
"text": "Example tweet content...",
"author": {
"id": "44196397",
"name": "Elon Musk",
"username": "elonmusk"
},
"public_metrics": {
"like_count": 1200,
"quote_count": 10,
"reply_count": 42,
"retweet_count": 150
}
}
}Endpoint
Quality
Full OpenAPI 3.1 schema with clear parameter definitions and pricing. The 402 challenge was captured and confirms the endpoint is live. However, no response schema is documented for this specific endpoint (200 just says "Success"), and no example response body is provided in the spec, so the example response above is inferred from the landing page description of X v2-compatible JSON.
Warnings
- —No response schema defined for the 200 response — the example response is inferred, not documented.
- —The /docs, /pricing, and other sub-pages return 'Cannot GET' — documentation beyond the landing page and OpenAPI spec is unavailable.
- —Some sibling endpoints require Twitter session cookies (auth_token, ct0) passed as query parameters, which raises security concerns for those write endpoints.
Citations
- —The /tweets/by/id endpoint costs $0.0025 USDC per requesthttps://x402.twit.sh
- —Payment is in USDC on Base mainnet via x402 protocolhttps://x402.twit.sh
- —Data is returned in X v2 API-compatible JSON formathttps://x402.twit.sh
- —No account or API key is required; agents pay per requesthttps://x402.twit.sh
- —twit.sh is compatible with Claude Code, Cursor, OpenClaw, Hermes, Codex and other AI agentshttps://x402.twit.sh
- —The endpoint accepts a required 'id' query parameter (numeric tweet ID)https://x402.twit.sh