# ReadX — X/Twitter User Info API

> ReadX — X/Twitter User Info API is a paid API for AI agents from readx.sh, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Fetches a Twitter/X user's basic profile info (id, bio, follower/following counts, verification status) by username, paid per call via x402 micropayments

## Facts

- Endpoint: GET https://readx.sh/api/%7Bname%7D/info
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-x-twitter-user-info-api-4f77bd33
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2Wj12OuDaQRhqEgnNQjOW

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 readx-x-twitter-user-info-api-4f77bd33
```

Example prompt: Can you pull up the X profile info for the user 'jack' — I want their follower count, bio, join date, and verification status?

## When to prefer this

Choose this endpoint when you need structured Twitter/X user profile data (bio, follower counts, verification, join date) without setting up official X API keys. It's ideal for one-off or low-volume lookups where per-call USDC micropayments via x402 are preferable to a subscription, and when you want a clean JSON response without OAuth complexity.

## Known failure modes

- Username not found — API returns non-zero code or empty data
- User account suspended — data reflects suspended:true with limited fields
- Rate limiting or payment failure — x402 payment not accepted, request rejected
- Malformed username input — URL path parameter missing or invalid
- Protected account — profile may return limited data with protected:true

## How this service works

ReadX is a read-only X/Twitter JSON API. Profiles, timelines, tweets, search, lists, followers & following — pay per call with x402 micropayments in USDC on Base or Solana. No API keys.

## Output

A JSON object with code 0 and a data object containing: numeric user ID, bio text, like count, media count, banner URL, tweet count, profile picture URL, website, full name, join date (Unix timestamp), location, username, follower count, following count, protected flag, suspended flag, pinned tweet ID, and verified type (e.g. 'Blue').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "code": 0,
  "data": {
   "id": "12",
   "bio": "",
   "likes": 39744,
   "media": 2968,
   "banner": "",
   "tweets": 30715,
   "userPic": "",
   "website": "",
   "fullname": "jack",
   "joinDate": 1142974214,
   "location": "",
   "username": "jack",
   "followers": 6500000,
   "following": 4000,
   "protected": false,
   "suspended": false,
   "pinnedTweet": "1833951636005552366",
   "verifiedType": "Blue"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-x-twitter-user-info-api-4f77bd33/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from readx.sh](https://www.zero.xyz/host/readx.sh/llms.txt)