X (Twitter) Mutual Follow & Relationship Checker

Check whether two X / Twitter accounts follow each other in either direction. One comparison shows whether the relationship is mutual, one-way, or neither.

Enter usernames, @handles, full profile URLs, numeric user IDs, or a mixture of these formats. No X login, cookies, API key, or proxy configuration is required.

What can this Actor do?

• Check both follow directions with one run.
• Distinguish mutual follows, one-way follows, and no follow relationship.
• Resolve usernames, X/Twitter profile URLs, and stable numeric user IDs.
• Return readable summaries for people and structured fields for APIs and automations.
• Export the result as JSON, CSV, Excel, XML, or RSS from the Apify Dataset.
• Automate recurring checks with Apify Tasks, schedules, webhooks, API, and integrations.

Use it for social-graph research, creator and brand relationship checks, outreach qualification, public-account monitoring, and workflow validation.

How to use

1. Enter First account (A).
2. Enter Second account (B).
3. Click Start.
4. Open the Dataset Overview to see both follow directions.

Each account can be entered as:

• Username: elonmusk
• Handle: @elonmusk
• Profile URL: https://x.com/elonmusk
• Numeric user ID: 44196397

Input

{
  "firstAccount": "elonmusk",
  "secondAccount": "SpaceX"
}

Both fields are required and must identify two different accounts. This Actor compares one account pair per run.

Output

Each run stores one Dataset item. The human-readable relationship_summary gives the answer directly, while the boolean fields and relationship_type support filtering and automation.

{
  "status": "success",
  "message": "",
  "relationship_summary": "@elonmusk and @SpaceX follow each other.",
  "relationship_type": "mutual",
  "checked_at": "2026-10-11T05:06:46.950550Z",
  "first_account_requested": "elonmusk",
  "first_account_user_id": "44196397",
  "first_account_username": "elonmusk",
  "first_account_profile_url": "https://x.com/elonmusk",
  "second_account_requested": "SpaceX",
  "second_account_user_id": "34743251",
  "second_account_username": "SpaceX",
  "second_account_profile_url": "https://x.com/SpaceX",
  "first_follows_second": true,
  "second_follows_first": true,
  "mutual_follow": true
}

Relationship types

relationship_type	Meaning
mutual	Account A and account B follow each other.
first_follows_second	Account A follows account B, but account B does not follow account A.
second_follows_first	Account B follows account A, but account A does not follow account B.
neither	Neither account follows the other.

Invalid or unavailable accounts

Invalid input does not produce a misleading relationship. The Dataset item uses status: "invalid_input", explains what to correct in message, and leaves relationship values as null.

If X reports that either account does not exist, is suspended, or is unavailable, the result uses status: "account_unavailable". Temporary request failures use status: "request_failed".

Automate X follow relationship checks

Save any account pair as an Apify Task and run it on a schedule to monitor whether the relationship changes. Use webhooks to notify another service after a run, or consume the structured Dataset result through the Apify API, Make, Zapier, Google Sheets, or your own application.

The Actor can also be exposed to AI clients through the Apify MCP Server:

https://mcp.apify.com/?tools=arjun_code/x-twitter-follow-relationship-checker

How much does an X follow relationship check cost?

The Actor uses pay-per-event pricing. One relationship-check-result event is charged only when both accounts are resolved and a follow relationship is successfully saved. invalid_input, account_unavailable, and request_failed rows are not charged as successful checks.

Apify plan	Per successful check	Per 1,000 successful checks
Free	$0.00050	$0.50
Bronze	$0.00045	$0.45
Silver	$0.00040	$0.40
Gold	$0.00035	$0.35
Platinum	$0.00035	$0.35
Diamond	$0.00035	$0.35

An apify-actor-start event costs $0.00005 per run. Platform usage is included in the configured event prices. The Pricing tab is the source of truth if prices change later.

Run with the API

curl -X POST \
  "https://api.apify.com/v2/acts/arjun_code~x-twitter-follow-relationship-checker/runs" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"firstAccount":"elonmusk","secondAccount":"SpaceX"}'

The run output contains a link to the default Dataset, where the result can be previewed, downloaded, or consumed by another workflow.

Related X / Twitter Actors

Actor	Best for
X Followers & Following Scraper	Exporting the available followers or following of public accounts
X People Search Scraper	Finding X profiles by keyword and profile filters
X Account Origin Scraper	Checking account origin and public account metadata

Frequently asked questions

Do I need X cookies, an API key, or a proxy?

No. Enter the two accounts you want to compare. The Actor manages the required access and proxy routing.

Can I monitor a relationship over time?

Yes. Save the input as an Apify Task and attach a schedule. Each run returns a timestamped snapshot that can be sent to a webhook or another integration.

Does the result include the date an account followed another account?

No. X returns the current follow relationship, not the date when that relationship began.

What happens when an account does not exist or is suspended?

The Dataset returns status: "account_unavailable" with a readable message. It does not report a missing account as a valid no-follow relationship.

Where can I report a problem?

Open an issue on the Actor page and include the Run ID. Do not post private credentials or account cookies.

Important limitations

• The result is a current relationship snapshot, not historical data.
• X does not provide the date when either account followed the other through this operation.
• Deleted, suspended, restricted, or temporarily unavailable accounts may return account_unavailable.

This independent Actor is not affiliated with, endorsed by, or sponsored by X Corp.