# Twitter/X Follow Relationship Checker

> Twitter/X Follow Relationship Checker is a paid API for AI agents from twitter.surf.cascade.fyi, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Checks whether a follow relationship exists between two Twitter/X users

## Facts

- Endpoint: POST https://twitter.surf.cascade.fyi/api/v1/twitter/users/relationship
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/twitter-x-follow-relationship-checker-728c7d7b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pqBGyHtqBmbt6FchWZ1Oe

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 twitter-x-follow-relationship-checker-728c7d7b -d '<json body>'
```

Example prompt: Can you check if the Twitter user with ID 12345 follows the user with ID 67890, and also whether 67890 follows them back?

## When to prefer this

Use this endpoint when you need to programmatically verify Twitter follow relationships between specific users — especially useful for eligibility checks, social graph analysis, or verifying influencer/brand connections. Prefer this over scraping or manual checks when you need fast, reliable relationship data via a paid API with clear pricing.

## Known failure modes

- Invalid or non-existent user IDs return an error
- Private/suspended accounts may return restricted relationship data
- Rate limiting by the underlying Twitter API may cause failures
- Missing required user ID parameters return a validation error
- Payment failure (x402) if USDC balance is insufficient

## How this service works

Check follow relationship

## Output

Returns the follow relationship status between two Twitter users, including whether the source user follows the target and whether the target follows the source back (following/followed_by booleans, and potentially blocking/muting status).

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "source",
      "target"
     ],
     "properties": {
      "source": {
       "type": "string",
       "description": "Source user ID or username"
      },
      "target": {
       "type": "string",
       "description": "Target user ID or username"
      }
     }
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "data"
     ],
     "properties": {
      "data": {
       "type": "object",
       "required": [
        "following",
        "followed_by"
       ],
       "properties": {
        "following": {
         "type": "boolean"
        },
        "followed_by": {
         "type": "boolean"
        }
       }
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/twitter-x-follow-relationship-checker-728c7d7b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twitter.surf.cascade.fyi](https://www.zero.xyz/host/twitter.surf.cascade.fyi/llms.txt)
