# ReadX — X/Twitter Relations API

> ReadX — X/Twitter Relations 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).

Returns the bidirectional relationship status between two X/Twitter users, including follow, block, mute, and DM permission states.

## Facts

- Endpoint: GET https://readx.sh/api/%7Bname%7D/relations
- 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-relations-api-b9098499
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9NIzSFRZPzmxiK-L3sLen

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-relations-api-b9098499
```

Example prompt: Check whether the Twitter account 'jack' follows 'elonmusk' and if elonmusk follows back — also tell me if either of them is blocking or muting the other.

## When to prefer this

Choose this endpoint when you need to programmatically verify the follow/block/mute relationship between two specific X/Twitter users without managing X API keys. Ideal for social graph analysis, outreach eligibility checks, and mutual-follow detection. Prefer over the X official API when you want keyless micropayment access via USDC on Base or Solana.

## Known failure modes

- Unknown or suspended username returns an error or empty data
- Rate limiting or upstream X API unavailability causes a failed response
- Incorrect or misspelled username in the path yields a not-found error
- Payment failure (insufficient USDC balance) prevents the request from completing via x402

## 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 a 'data' field containing: source and target usernames, sourceFollowsTarget (boolean), targetFollowsSource (boolean), blocking (boolean), blockedBy (boolean), muting (boolean), and canDm (boolean). Also includes a top-level code field (0 = success).

## 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": {
   "canDm": false,
   "muting": false,
   "source": "jack",
   "target": "elonmusk",
   "blocking": false,
   "blockedBy": false,
   "sourceFollowsTarget": true,
   "targetFollowsSource": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readx-x-twitter-relations-api-b9098499/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)