x402basequality 0.82

Pay-per-request Twitter/X data API via x402 — user timelines, tweet lookup, search, and more for USDC on Base.

Price
per_call
Protocol
x402
Verified
no
Endpoint
https://x402.twit.sh/tweets/user

What it does

twit.sh is a payment-gated Twitter/X data API that uses the x402 protocol for per-request micropayments in USDC on Base mainnet. No API keys, OAuth flows, or account creation required — agents pay inline with each HTTP request. The specific endpoint `/tweets/user` returns up to 20 tweets from a user's timeline (most recent first) given a screen name, with pagination support via `next_token`.

The broader API covers over 25 endpoints across tweets, users, lists, communities, and articles. Read-only endpoints include user profile lookup (by username, ID, or bulk), tweet lookup (single or bulk), tweet search with advanced filters (date range, engagement minimums, hashtags, mentions), quote tweets, replies, retweets, follower/following lists, list details/members/tweets, community details/members/posts, and full X Article content in Markdown. Authenticated write endpoints (requiring Twitter session cookies) support creating/deleting tweets, liking, bookmarking, retweeting, and following/unfollowing.

Pricing ranges from $0.0025 to $0.01 USDC per request depending on the endpoint. The `/tweets/user` endpoint costs $0.01 USDC per call. All responses use X v2 API-compatible JSON format. The data is sourced from publicly available profile and post information on the open web. The API is designed for autonomous AI agents — compatible with Claude Code, Cursor, OpenClaw, Hermes, Codex, and others. An npm CLI skill (`npx twitsh`) is also available for easy agent integration.

Capabilities

twitter-user-timelinetwitter-user-lookuptwitter-tweet-lookuptwitter-tweet-searchtwitter-followerstwitter-followingtwitter-quote-tweetstwitter-repliestwitter-retweetstwitter-list-datatwitter-community-datatwitter-article-contenttwitter-create-tweettwitter-like-bookmark-retweettwitter-follow-unfollowbulk-user-lookupbulk-tweet-lookupx402-micropaymentusdc-on-basepagination

Use cases

  • —AI agents autonomously fetching a user's latest tweets for summarization or monitoring
  • —Building social media dashboards that pull Twitter profile and engagement data on demand
  • —Searching Twitter's full archive with advanced filters for research or trend analysis
  • —Retrieving X Community posts and members for community analytics
  • —Automating Twitter actions (like, retweet, follow) via agent workflows with session credentials

Fit

Best for

  • —AI agents needing Twitter/X data without API key management
  • —Developers who want pay-per-call pricing instead of monthly X API subscriptions
  • —Autonomous workflows that need to read and write to Twitter programmatically
  • —Quick one-off Twitter data lookups without account setup

Not for

  • —High-volume bulk data collection requiring millions of calls (costs add up at $0.01/call)
  • —Applications requiring official Twitter API compliance or OAuth user consent flows
  • —Use cases needing real-time streaming of tweets (this is a request-response API)

Quick start

# Fetch latest tweets from a user's timeline
curl -X GET "https://x402.twit.sh/tweets/user?username=elonmusk" \
  -H "X-PAYMENT: <x402_payment_proof>"

Example

Request

{
  "url": "https://x402.twit.sh/tweets/user?username=elonmusk",
  "method": "GET",
  "headers": {
    "X-PAYMENT": "<x402_payment_proof>"
  }
}

Endpoint

URLhttps://x402.twit.sh/tweets/user
Transporthttp
Protocolx402
Pay to0x9dBA414637c611a16BEa6f0796BFcbcBdc410df8
CurrencyUSD COIN

Quality

0.82/ 1.00

Full OpenAPI 3.1 schema with 25+ endpoints, clear pricing in USDC, live 402 challenge confirmed, and a well-documented landing page. Deducted because response schemas are mostly absent (only write endpoints have partial schemas), no example response bodies are provided, and /docs returns 404.

Warnings

  • —Response schemas are not documented for most read endpoints — actual response structure must be inferred from 'X v2 API-compatible JSON' claim
  • —Authenticated write endpoints require raw Twitter session cookies (auth_token, ct0) passed as query parameters, which is a security concern
  • —The /docs, /api, /pricing, and /README paths all return 404
  • —No rate limit information is documented in the available material

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:25:29Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/AzvQ2w