# AIsa Payment Gateway - Twitter User Relationship Check

> AIsa Payment Gateway - Twitter User Relationship Check is a paid API for AI agents from pay.lnpay.ai, paid per call via x402, $0.0018/call, status unknown (last checked 2026-09-13).

Checks whether a source Twitter/X user is following or is followed by a target Twitter/X user.

## Facts

- Endpoint: GET https://pay.lnpay.ai/twitter/user/check-relationship
- Price: $0.0018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/aisa-payment-gateway-twitter-user-relationship-check-309bb07c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7LexOimQISkRzj7iGKLoN

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 aisa-payment-gateway-twitter-user-relationship-check-309bb07c
```

Example prompt: Can you check on Twitter whether the user 'elonmusk' is following or is followed by 'sama'?

## When to prefer this

Use this endpoint when you need to programmatically verify the follow/follower relationship between two specific Twitter/X users by their screen names, especially within automated workflows or social graph analysis tasks.

## Known failure modes

- Invalid or non-existent screen name returns an error or empty result
- Rate limiting from the underlying Twitter API causing temporary failures
- Authentication or payment failure for x402 protocol resulting in 402 response
- Suspended or deactivated Twitter accounts may return errors or unexpected results

## How this service works

Check if the user is following/followed by the target user.

## Output

Returns a relationship status object indicating whether the source user is following the target user and/or whether the target user is following the source user back.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "source_user_name",
  "target_user_name"
 ],
 "properties": {
  "source_user_name": {
   "type": "string",
   "description": "screen name of the source user"
  },
  "target_user_name": {
   "type": "string",
   "description": "screen name of the target user"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/aisa-payment-gateway-twitter-user-relationship-check-309bb07c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pay.lnpay.ai](https://www.zero.xyz/host/pay.lnpay.ai/llms.txt)
