Get paginated replies to any tweet via x402 micropayment — $0.01 USDC per call on Base.
What it does
The `/tweets/replies` endpoint on twit.sh returns paginated reply posts for a given tweet, identified by its numeric tweet ID. It is part of a broader payment-gated Twitter/X data API that returns X v2 API-compatible JSON. No API key or account is required; instead, the endpoint uses the x402 protocol where agents pay $0.01 USDC per request on Base mainnet.
When an unauthenticated GET request is made, the server responds with HTTP 402 and a machine-readable payment challenge specifying the USDC amount and recipient address. The caller settles the payment on-chain, retries with an `X-PAYMENT` proof header, and receives the reply data. Pagination is supported via a `next_token` cursor parameter.
This endpoint is one of many on twit.sh covering tweets, users, lists, communities, and articles. The API also offers authenticated write operations (like, retweet, bookmark, follow, create/delete tweets) that require Twitter session cookies. The replies endpoint itself is read-only and requires only the tweet ID. Data is sourced from the open web and shaped into clean JSON. The service is available as an npm CLI skill (`npx twitsh`) compatible with Claude Code, Cursor, OpenClaw, and other AI agents.
Capabilities
Use cases
- —Retrieve all replies to a specific tweet for sentiment analysis or conversation monitoring
- —Build agent workflows that track discussion threads around key posts
- —Aggregate community feedback on announcements or product launches
- —Monitor reply volume and content for brand mentions on X/Twitter
Fit
Best for
- —AI agents that need Twitter reply data without API key management
- —Pay-per-request tweet conversation retrieval
- —Autonomous agent pipelines on Base mainnet using x402
- —Lightweight social media monitoring without OAuth setup
Not for
- —High-volume bulk scraping (pay-per-call cost adds up)
- —Write operations like posting replies (use the /tweets POST endpoint instead)
- —Users who need free or subscription-based Twitter API access
Quick start
# 1. First request returns 402 with payment challenge
curl 'https://x402.twit.sh/tweets/replies?id=1110302988'
# 2. After settling USDC payment on Base, retry with proof:
curl -H 'X-PAYMENT: 0x<payment_proof>' \
'https://x402.twit.sh/tweets/replies?id=1110302988'Endpoint
Quality
Full OpenAPI schema with clear parameter definitions and pricing is available. The endpoint is confirmed live (402 challenge captured). However, no response schema or example response body is documented for this specific endpoint, and the /docs path returns 404, so the exact shape of reply data must be inferred from the "X v2 API-compatible" claim.
Warnings
- —No response schema documented for the 200 response on /tweets/replies — actual reply JSON structure is unspecified.
- —The /docs, /pricing, and /api paths all return 404, so there is no supplementary documentation beyond the landing page and OpenAPI spec.
- —The x402 challenge object captured is empty ({}), so the exact on-chain payment details (recipient address, token contract) are not confirmed in the probe.
Citations
- —The /tweets/replies endpoint costs $0.01 USDC per requesthttps://x402.twit.sh
- —Payment is in USDC on Base mainnet via the x402 protocolhttps://x402.twit.sh
- —All endpoints return X v2 API-compatible JSONhttps://x402.twit.sh
- —No account or API key is required; agents pay per requesthttps://x402.twit.sh
- —The endpoint accepts id (numeric tweet ID) and optional next_token for paginationhttps://x402.twit.sh
- —twit.sh is available as an npm CLI skill via npx twitshhttps://x402.twit.sh