# ReadX Affiliates API

> ReadX Affiliates 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-16).

Returns accounts affiliated with a given X/Twitter user, such as an organization's member accounts

## Facts

- Endpoint: GET https://readx.sh/api/:name/affiliates
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readx-affiliates-api-5e30991d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vqXxR1edokFtOkg6jTEC9

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-affiliates-api-5e30991d
```

Example prompt: Can you pull up all the accounts affiliated with the Twitter user 'nasa' — like any member or org-linked handles associated with that account?

## When to prefer this

Use this endpoint when you need to discover accounts organizationally affiliated or linked to a specific X/Twitter user — such as finding an organization's member handles. Prefer this over the profile or followers endpoints when the goal is specifically to enumerate affiliated/member accounts rather than who follows or is followed by the user.

## Known failure modes

- Invalid or non-alphanumeric X handle returns a 400 or validation error
- Non-existent X username returns an empty list or 404
- Rate limiting or upstream X API unavailability returns a 5xx error
- Missing required 'name' query parameter causes a schema validation failure
- Private or suspended accounts may return no affiliates

## How this service works

Accounts affiliated with a user (e.g. an organization's members). Example: GET /api/jack/affiliates

## Output

A JSON object listing accounts affiliated with the specified X/Twitter user, including member or organizationally linked accounts (e.g. subsidiary handles, org members). Typical fields include user profile info such as handles, display names, and account metadata for each affiliated account.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "name"
     ],
     "properties": {
      "name": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_]+$",
       "minLength": 1,
       "description": "X handle without the leading @ (alphanumeric and underscore)."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

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