A clean JSON mirror of X — profiles, timelines, tweets, search, lists, followers and following. No API keys, no signup, no rate-limit dashboards. Just $0.05 per request in USDC on Base or Solana, settled over x402.
ReadX ships an agent-readable skill file. Point any x402- or MPP-capable agent at the URL below and it learns every endpoint, the payment flow, and how to read X data — paying per call from its own wallet.
Or fetch it directly: curl https://readx.sh/skill.md
The same /api endpoints, paid two ways — switch the tab to pay via x402 (readx.sh) or MPP (mpp.readx.sh). Most responses are JSON wrapped as {"code":0,"data":…} on success; GetXAPI routes (followers, following, articles) pass the upstream payload through verbatim. Expand an endpoint for parameters, an example response, and a live "Try it" link.
Base URL https://readx.sh/api
Everything about an account: timeline, bio, stats, followers, following and metadata.
Single tweets, their full conversation threads, and edit history.
Full-text search across tweets and users.
Curated X lists — metadata, their timeline, and their members.
Spaces and live broadcasts.
Long-form X articles, via the GetXAPI provider.
Both protocols turn the dormant HTTP 402 status into a real payment rail. No accounts, no invoices — your client pays for exactly what it calls. Pay via x402 at readx.sh, or the same endpoints via MPP at mpp.readx.sh.
Call any endpoint. Costly ones reply 402 with a payment challenge — x402 in the PAYMENT-REQUIRED header (apex host), MPP in the WWW-Authenticate header (mpp. host).
Your client signs a $0.05 USDC payment on Base or Solana and retries — x402 via the X-PAYMENT header, MPP via the Authorization credential.
The facilitator settles on-chain and the API returns your JSON — no keys, no accounts.