# ReadX Get User IDs

> ReadX Get User IDs 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).

Resolves one or more X/Twitter usernames to their numeric user IDs in a single call

## Facts

- Endpoint: GET https://readx.sh/api/tools/get_user_ids
- 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-get-user-ids-0d4c4b58
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ol8xcjtxkeO6eVAHJsZFq

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-get-user-ids-0d4c4b58
```

Example prompt: Look up the numeric Twitter user IDs for the usernames 'jack' and 'elonmusk' — I need the raw IDs to pass into another tool.

## When to prefer this

Use this endpoint when you need to resolve Twitter/X usernames to numeric user IDs without obtaining official Twitter API credentials. It is especially useful for enriching datasets, validating account existence, or preparing IDs for downstream Twitter data calls. Prefer it over the official Twitter API when you want instant pay-per-call access with no key management overhead.

## Known failure modes

- Username does not exist — returned as null in the data map rather than an error
- Payment failure or insufficient USDC balance — x402 payment rejected before the call completes
- Malformed or empty username input — may return an error code
- Rate limiting or temporary X/Twitter backend unavailability — may return a non-zero error code

## How this service works

Resolve up to 20 @handles to numeric user ids (map; null on per-handle failure). Example: GET /api/tools/get_user_ids?usernames=jack,elonmusk

## Output

Returns a JSON object with a code (0 = success) and a data map where each requested username is a key whose value is either the numeric Twitter user ID string or null if the account does not exist.

## 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": {
   "jack": "12",
   "elonmusk": "44196397",
   "thisuserdoesnotexistzzz": null
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-get-user-ids-0d4c4b58/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)