# ReadX Search Users API

> ReadX Search Users 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-14).

Search for X/Twitter user accounts by keyword or query, returning profile data including follower counts, verification status, and profile URLs

## Facts

- Endpoint: GET https://readx.sh/api/search/users
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-search-users-api-d5b1ac0d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OC5VSMKKPaMoxcmXqiLoy

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-search-users-api-d5b1ac0d
```

Example prompt: Search X/Twitter for users matching 'AI researcher' and give me their usernames, follower counts, and whether they're verified — use ReadX and page through the results if there are more.

## When to prefer this

Use this endpoint when you need to search X/Twitter for user accounts by keyword without managing API keys, prefer pay-per-call micropayments via x402 in USDC, and need structured JSON profile data including follower counts and Blue verification status. Prefer over official Twitter API when avoiding OAuth setup or when operating in a crypto-native agent pipeline.

## Known failure modes

- Payment not included or insufficient USDC — returns 402 Payment Required
- Invalid or missing search query parameter — returns 400 Bad Request
- Rate limit or quota exceeded — returns 429 Too Many Requests
- No users found matching the query — returns empty users array with has_more: false
- Invalid cursor token for pagination — may return 400 or empty results

## How this service works

Search for users by query (paginate with cursor until has_more is false). Example: GET /api/search/users?q=jack

## Output

A JSON object containing an array of user profiles, each with fields: id, url, name, type, userName, followers, following, isVerified, isBlueVerified — plus a has_more boolean and a next_cursor string for pagination.

## 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": {
   "users": [
    {
     "id": "99",
     "bio": "",
     "likes": 0,
     "media": 0,
     "banner": "",
     "tweets": 30000,
     "userPic": "",
     "website": "",
     "fullname": "Someone",
     "joinDate": 1142974214,
     "location": "",
     "username": "someone",
     "followers": 599,
     "following": 307,
     "protected": false,
     "suspended": false,
     "pinnedTweet": "0",
     "verifiedType": "Blue"
    }
   ]
  },
  "pagination": {
   "has_more": true,
   "next_cursor": "DAABCgABG...cursor"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-search-users-api-d5b1ac0d/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)