> **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, 910 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`). --- # Read your Listening results (https://www.socialfetch.dev/docs/tools/listening/read-your-results) ## The preview ### The summary At the top: how many posts it found, on which platforms, and what it cost, such as *730 posts on X, Instagram, Reddit and 5 more · 183 credits*. Hover the credits to see the limit; anything under it isn't charged. Searching the same query again with the same settings shows **Already ran: not charged again**. **Keep listening** saves it as a topic. See [Your first topic](/docs/tools/listening/your-first-topic#5-keep-listening). ### Where it's said The share of posts on each platform. Under it, each platform that didn't search everything says why: | Note | What it means | | ----------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | **Stopped at your credit limit. A higher limit reads further back.** | It found posts, then used its share of the limit. Raise **Spend** to read further back. | | **Stopped at your credit limit. A higher limit searches every term.** | The limit didn't cover a search for every term. Raise **Spend**. | | **Reached your credit limit before finding any.** | Its share ran out before it found a post. | | **Searched #a, #b.** | Instagram searched these hashtags. | | **No mentions in the latest N posts.** | It read its newest posts, and none matched your query. | | **No recent posts use these hashtags.** / **No recent posts here mention it.** | Nothing recent on that platform. | | **Read N, M left out as noise.** | **Leave out** dropped some posts it read. | | **Ran out of time, so it may have missed some. What it found is shown.** | A search takes up to about a minute; this platform didn't finish. | | **The platform didn't answer just now. Preview again later.** | That platform failed this time. Nothing was charged for it. | | **Nothing in the query can be searched here.** | Your query uses something this platform can't search, such as a field it doesn't have. | Platforms that ended the same way share one note. ### Filters and order * **Platform** tabs: all posts, or one platform's. * With sentiment on: a bar showing the split, and **Positive**, **Neutral** and **Negative** to filter. * With insights on: **About {name}** and **Not about it**, **Need a reply**, **Risk**, a **kind** menu and your own questions. See [Sentiment and insights](/docs/tools/listening/sentiment-and-insights). * **Newest first** or **Most reach (estimated)**. Reach is estimated from a post's views, or its author's followers, or the community's members, whichever the platform gives; posts without any go last. Hover a post's reach to see which. ### Notes on a post | Note | What it means | | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | | **Matched gymshark** | The words in your query this post matched. Words every post matched aren't repeated. | | **Might match: {Platform} doesn't give a post's language, so that part of the query wasn't checked.** | Your query checks something this platform doesn't return. The rest of the query matched. | | **+2 reposts**, **+1 similar post** | Reposts and near-copies of the post, folded under it. Click to see them. | | **Repost of an earlier post** / **Repeat of an earlier post** | A copy of a post you've already seen. | | **In passing**, **Complaint**, **Needs reply**, **Risk** | Insights' judgements. See [Sentiment and insights](/docs/tools/listening/sentiment-and-insights). | ## A topic's page ### At the top * The topic's name and status: **Active**, **Paused**, **Capped** (its monthly cap is spent) or **Failing** (its last 5 runs failed). A paused, capped or failing topic says why, and what to do. * **Needs attention**: a spike, a volume alert, and, with insights, how many posts need a reply or are a risk in the last 30 days. Click one to see those posts. * The summary: **posts kept** (each post once, for a year), new in the last 7 days, **credits this month**, and the last run. * The latest **briefing**, if it has one. ### Posts per day, Where it's said, Loudest voices * **Posts per day**: the last 30 days, by platform, with the busiest day. * **Where it's said**: every post it has kept, by platform. * **Loudest voices**: the accounts it heard most from. Click one to see only their posts. ### Posts and Runs * **Posts**: everything it kept, newest first, with the same filters as the preview, plus **Search posts** for words in a post. They come 25 to a page, with **Previous** and **Next**. Correct a post's sentiment or relevance from the **⋯** at its top right. * **Runs**: the latest 20, newest first: when it started (**Scheduled** or **Run by hand**), its status, how many posts matched, how many were new, and its credits. **Partial** means some platforms stopped short: it shows their logos, and pointing at it says why (the run's credit limit, time, or a platform that didn't answer). What they found is kept. ### Spikes A **spike** is far more posts in a day than usual: at least 20 posts in 24 hours, well above the topic's usual daily count over the past 14 days and at least twice it. It's shown as, for example, *Spike: 64 posts in 24 hours, usually about 12 a day*. A topic needs 7 days of history before it can spike, and spikes at most once a day. With insights on, only posts about the topic count. ### What each run searches A topic's first run reads each platform's newest posts, up to its credits per run. After that, each run searches from shortly before the last one, so it finds what's new, and keeps a post only the first time it sees it. Reposts and near-copies are grouped with posts it kept in the last 7 days. - [Sentiment and insights](/docs/tools/listening/sentiment-and-insights) — Feelings, posts that aren't about it, and what needs a reply. - [Alerts and exports](/docs/tools/listening/alerts-and-exports) — Volume alerts, briefings, webhooks and downloads.