> **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`). --- # Track your first X account (https://www.socialfetch.dev/docs/tools/follower-tracker/track-your-first-account) This guide tracks a real account from start to finish. It uses `@biomejs`, the account of a developer tool with about 10,000 followers, but any public account works the same way. You'll finish with the account's whole audience collected and a schedule that checks it for changes. ## Step 1: Open the tracker Sign in to the [Social Fetch app](https://app.socialfetch.dev). In the top menu, open **Tools** and choose **X Follower Tracker**. ## Step 2: Look up the account The first time you open the tracker, it asks which account you want to see. Type the handle in the box and click **Preview**. If you already track other accounts, click **Track an account** at the top right instead. You can type the account in any of these ways: * the handle on its own: `biomejs` * the handle with an @: `@biomejs` * the profile link: `x.com/biomejs` or `https://twitter.com/biomejs` Use the handle, not the display name. Handles are the part after the @: up to 15 letters, numbers and underscores, with no spaces. If the tracker says **Enter an X handle or public profile URL**, check for a space, a typo or a display name. The tracker opens **Track an X account** and looks the account up. Check the profile card under the handle box to make sure it's the account you meant: the name, picture, bio and follower count come straight from X. Looking up an account uses 1 credit; clicking **Preview** and the lookup that follows count once. To try a different account, change the handle and click **Look up** again, which uses another credit. ## Step 3: Choose what to track Under **Set up tracking**, make two choices: 1. **What to track.** **Full audience** collects every follower, so you can see who followed and who left. **Follower count only** just records the number each time, and costs much less. Choose Full audience unless you only care about the count. 2. **How often.** **Daily** suits most accounts. **Every 6 hours** shows changes sooner and costs four times as much. **Weekly** is the cheapest. As you choose, the **Your tracked account** panel on the right updates the cost of the first check and of a month of checks. ## Step 4: Check the extras and limits Open **Extra data and limits**. Three extras start switched on: * **Following list** also collects who the account follows, so you can see mutual follows. It adds a little to every check. * **Post context** collects the account's recent posts, so you can line up posts with growth. * **AI insights** labels followers by role and topic, lets you filter the audience in plain English, and picks out highlights after each check. Your private notes and tags are never sent to it. Turn off anything you don't need. You can change all of these later. Below them, **Most credits one check can use** sets a limit for each check: one for follower lists, one for profile details and one for posts. They start at 100, 100 and 10 credits. When you look up a big account, the tracker raises the follower lists limit to fit its size, so you can usually leave these as they are. If a check does reach a limit later, it stops and keeps everything it already collected. [Costs and limits](/docs/tools/follower-tracker/costs-and-limits) explains each one. The section above it, **Alerts and goal**, sets up email alerts and a follower goal. The alerts all start switched off. See [Alerts and exports](/docs/tools/follower-tracker/alerts-and-exports). ## Step 5: Start tracking Check the panel on the right one last time. **First check** is the most the first check can cost; it's the biggest because it collects the whole audience and fills in profile details. **Each month** estimates the regular checks after it. When you're happy, click **Start tracking**. If your balance is lower than the first check, the panel says so. You can still start: the first check collects what your credits allow, and you can carry on later. See [When a check stops](/docs/tools/follower-tracker/costs-and-limits#when-a-check-stops). ## Step 6: Let the first check run The tracker opens the account's page and starts the first check. A progress bar shows each stage: the account, its followers, their profile details, recent posts, AI labels and, finally, Ready. The check runs in the background, so you can close the page and come back later. Collecting the followers is the quick part. Filling in names, bios and pictures takes longer, and the bigger the audience, the longer it takes. You don't have to wait for the end. As soon as every follower is collected, the title changes to **audience is ready to explore** and an **Explore audience** button appears. Names, bios and pictures keep filling in after that. ## What happens next The first check is the starting point, so it doesn't list anyone as a new follower. From the next scheduled check on, the account page shows who followed, who left and who came back. To see changes sooner, click **Check now** at the top of the account page once the first check has finished. Each extra check costs the same as a scheduled one. - [Read your results](/docs/tools/follower-tracker/read-your-results) — Growth, highlights and every change. - [Explore the audience](/docs/tools/follower-tracker/explore-the-audience) — Search and filter everyone who follows. - [Costs and limits](/docs/tools/follower-tracker/costs-and-limits) — Keep spending where you want it.