> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/docs/tools/follower-tracker/use-cases>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/tools/follower-tracker/use-cases.mdx>

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** <https://www.socialfetch.dev/openapi.json>

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 264 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# X Follower Tracker use cases (https://www.socialfetch.dev/docs/tools/follower-tracker/use-cases)

Each use case below is a short recipe built from the tracker's features. If you haven't tracked an account yet, start with [Track your first account](/docs/tools/follower-tracker/track-your-first-account).

## Watch a competitor's audience

See who is paying attention to a competitor, and who leaves them.

1. Track the competitor's account with **Full audience**, checked **Daily**.
2. Track your own account too, so you can compare them.
3. On the tracker home page, use **Compare audiences** to see how many followers you share and how many are unique to each of you. The people unique to them are people you haven't reached yet.
4. On the competitor's **Audience** tab, click **New this week** to see who started following them recently. Combine it with **10k+ followers** or **Verified** to find the notable ones.
5. Save that view as a segment, for example *New and notable*, and check it each week.
6. Watch the **Changes** tab for people who leave them. Someone who just unfollowed a competitor may be looking for an alternative.

## Grow your own account

Find out what brings followers in and what makes them leave.

1. Track your account with **Post context** switched on.
2. Set a **Follower goal** under **Alerts and goal** to see your progress on the account page.
3. On the **Overview** tab, the follower chart marks your posts as dashed lines. Look for jumps in followers after particular posts. A post and a jump close together don't prove the post caused it, but a pattern over several weeks is worth acting on.
4. Read the **Highlights** after each check for the changes worth knowing about.
5. Switch on **Growth alert** and **Departure alert** with numbers that would be unusual for your account, so you hear about sudden changes.
6. Look at **Common in bios** on the **Audience** tab to see who your account appeals to, and whether that matches who you want to reach.

## Keep track of the people who matter

Know when an investor, customer, journalist or partner follows or leaves.

1. Find each person in the **Audience** tab and click the star beside them, or **Watch** in their profile.
2. Add **Private notes** and tags in their profile, such as *Customer* or *Met at a conference*, so your team has the context.
3. Switch on **Watchlist alerts** under **Alerts and goal** to get an email when one of them follows or leaves.
4. Use **Watchlist** on the **Audience** tab to see everyone you're watching in one place.

You can only watch people the tracker has already collected: the account's followers, or the accounts it follows if **Following list** is on. To spot someone new, check **New this week** or switch on the weekly digest.

## Check an account before a partnership

Before paying for a sponsorship or partnership, check that an account's audience is real and relevant.

1. Track the account with **Full audience** and **Weekly** checks. You only need the first check, so pause or remove the account once you've decided.
2. When the first check finishes, look at **Common in bios** to see what its followers talk about.
3. Click the quick filters: **No bio** and **Accounts under 30 days old** show how many followers look like empty or new accounts. **Verified** and **10k+ followers** show how many notable people follow it.
4. With **AI insights** on, filter by **Role** or **Topic** to see whether the audience is the kind of people you want to reach.
5. Export the **Audience** or an **Account summary** to share with your team.
6. When you've decided, **Remove** the account, or **Pause** it to keep its history without spending more credits.

## Report to clients

Agencies can track client and competitor accounts in one workspace.

1. Track each client's account and its main competitors.
2. Switch on the **Weekly digest** for each account, so you get a summary every Monday.
3. Each month, export the **Account summary** and **Change history** to build a report.
4. Set a monthly cap in **Tracker spending** so spending across all clients stays predictable. See [Costs and limits](/docs/tools/follower-tracker/costs-and-limits#set-a-monthly-cap).

Owners and admins in the workspace see every tracked account; members see the accounts they added.

## Track growth cheaply

If you only need the follower count over time, for many accounts or for a long time, choose **Follower count only** and switch off **Post context**. Each check costs 1 credit, and the chart and goal still work. You won't see who followed or left. You can switch an account to **Full audience** later; the first full check then records the audience as its starting point.

- [Track your first account](/docs/tools/follower-tracker/track-your-first-account) — The step-by-step tutorial.

- [Explore the audience](/docs/tools/follower-tracker/explore-the-audience) — Filters, watchlist and segments.

- [Costs and limits](/docs/tools/follower-tracker/costs-and-limits) — Plan what each recipe costs.