> **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):** - **Markdown (.mdx) URL:** ## 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:** ## 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`). --- # Explore an X account's audience (https://www.socialfetch.dev/docs/tools/follower-tracker/explore-the-audience) The **Audience** tab lists everyone who follows the tracked account, from the first check onwards. It needs **Full audience** tracking; an account tracked by count only has no list to explore. Along the top are four views: **Everyone**, **Watchlist**, **Mutuals & follow-backs** and **Segments**. ## Search and filter everyone **Everyone** starts with the biggest accounts first. Narrow it down in three ways: 1. **Search** names and bios. 2. Open **Filters** for follower counts, words in the bio, location, verified badges, your own tags and, with AI insights on, topic and role. 3. Click a **quick filter**: **10k+ followers**, **Verified**, **New this week**, **Accounts under 30 days old** or **No bio**. Click it again to turn it off. **Common in bios** shows the words that come up most often in followers' bios, with how many bios include each one. Click a word to see just those people. It's a quick way to see what an audience is made of. The line above the list counts the matches and how many have **profile details**: name, bio, picture and follower count. The first check fills in details for as many people as the profile details limit allows, then keeps going on later checks. Until someone's details are in, their row says **Profile details not collected yet**, and filters on bios, locations or follower counts can't match them. ## Describe who you want With **AI insights** switched on, the Filters window has a box at the top: **Describe who you want**. Type what you're looking for in plain English and click **Apply**, for example: * *Developers with over 1,000 followers* * *Founders* * *Verified accounts with under 500 followers* The AI turns your description into the ordinary filters below the box, so you can see exactly what it chose and change anything that's wrong. It understands a fixed set of words about roles, topics, follower counts, badges and dates. A description with anything else in it, such as a name, a handle or a link, isn't sent, and it never sees your notes. **Role** and **Topic** come from AI labels, which the tracker adds after it collects profile details. The labels are only set when the AI is very sure, so many people have none, and a role or topic filter shows fewer people than you might expect. You can set someone's labels yourself from their profile. If the box says **AI filters are unavailable**, use the filter controls directly. See [Troubleshooting](/docs/tools/follower-tracker/troubleshooting#ai-filters-are-unavailable). ## Open someone's profile Click anyone in a list to open their profile on the right. It shows their bio, location, website, when they joined X and their follower numbers, then: * **With @account**: when they started following the tracked account, or that they were already following before tracking began, and whether the account follows them back. * **Profile changes**: changes to their handle, bio or counts that the tracker noticed. * **Audience labels**: their AI labels, with **Correct audience labels** to set them yourself. * **Private notes**: notes and tags only your workspace can see. They're never sent to the AI or included in exports. * **Look deeper**: **Account history** and **Recent posts**, fetched live from X when you click. Each lookup uses credits. ## Keep a watchlist Star the people who matter to you: customers, investors, partners or rivals. Click the star beside anyone in a list, or **Watch** in their profile. **Watchlist** shows everyone you've starred, with their tags. Watched people get their profile details refreshed first, and you can get an email when one of them follows or leaves. See [Alerts and exports](/docs/tools/follower-tracker/alerts-and-exports). ## Save a segment A segment is a saved set of filters, such as *verified founders* or *new followers with 10k+ followers*. Set up a search or filters, click **Save as segment** and give it a name. **Segments** shows a card for each one with how many people match, how many joined in the last week and how many left. Click a card to see its people. To delete a segment, use the bin icon on its card; it's deleted straight away. ## Find mutuals and follow-backs With **Following list** switched on, **Mutuals & follow-backs** compares the account's followers with the accounts it follows: * **Mutuals**: people who follow the account and are followed back. * **@account doesn't follow back**: followers the account doesn't follow. * **Don't follow @account back**: accounts it follows that don't follow it. The lists fill in once the first check has collected the following list. If the following list is switched off, **Set up following list** opens the setting. ## Compare two accounts When you track two or more accounts, the tracker's home page shows **Compare audiences**. Choose two accounts to see how many followers they share, what share of each audience that is, and how many are unique to each. Both accounts need to have collected their audience. In this example, 1,723 people follow both `@biomejs` and `@PrettierCode`. That's 17.4% of Biome's audience but only 6.6% of Prettier's, so most of Prettier's followers don't follow Biome. Below the figures, a list shows the shared followers, or the people unique to either account. ## Download the audience **Export CSV** downloads the list you're looking at, with your filters applied. See [Exports](/docs/tools/follower-tracker/alerts-and-exports#export-to-csv). - [Use cases](/docs/tools/follower-tracker/use-cases) — Ways to put the audience to work. - [Alerts and exports](/docs/tools/follower-tracker/alerts-and-exports) — Watchlist alerts and CSV files. - [Costs and limits](/docs/tools/follower-tracker/costs-and-limits) — What profile details and lookups cost.