> **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/integrations/agentic-commerce>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/integrations/agentic-commerce.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`).

---
# Buy in AI chat (https://www.socialfetch.dev/docs/integrations/agentic-commerce)

AI assistants that sell through **Stripe agentic commerce** can find Social Fetch, recommend a credit pack and buy it for you in the chat. You confirm, the assistant pays with the card you already use with it, and the credits land on your Social Fetch account.

  A pack bought in chat is the same pack, at the same price, as one bought on our [pricing page](/pricing). Credits never expire and work on every [endpoint](/docs/api), [MCP](/docs/integrations/mcp) tool and SDK method.

## How it works

Social Fetch never sees your card: the assistant hands Stripe a single-use payment token, and we only learn that the payment succeeded and the email it was made with.

## What you can buy

All three pay-as-you-go packs are on sale in chat, at the same prices as the [pricing page](/pricing).

Monthly plans are listed too. Subscriptions start on our site, so the assistant links you to [pricing](/pricing) for those.

## Getting your credits

| You paid with…                         | What happens                                                                                                                                          |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| The email of your Social Fetch account | Credits are added straight away. We email you a link to create an API key.                                                                            |
| An email with no account yet           | We hold the credits and email you. [Sign up](https://app.socialfetch.dev/signup) with that exact address, verify it, and they're added automatically. |
| A different email than your account    | Reply to our email or [contact support](https://app.socialfetch.dev/support) and we'll move the credits.                                              |

Credits go to your personal workspace. To use them in a team workspace, ask [support](https://app.socialfetch.dev/support) to move them.

## Receipts and refunds

* **Receipt:** Stripe emails you a receipt for every purchase, as it does for any other card payment.
* **Refunds:** packs bought in chat follow the same [terms](/terms#billing) as dashboard purchases. If a refund is issued, the credits from that purchase are removed.
* **Disputes:** handled by Stripe like any card payment.

## Compared with other ways to pay

- [In AI chat](#how-it-works) — A person asks their assistant; a card pays for a credit pack. Best when you discover us inside the assistant.

- [Dashboard](/pricing) — Buy packs or a plan with your card, set up auto-refill, manage a team. Best for ongoing use.

- [x402](/docs/integrations/x402) — An agent pays USDC per request with no account at all. Best for autonomous agents.

## For AI agents

If you're an agent helping someone buy Social Fetch:

* Recommend a **pay-as-you-go pack** for one-off or uncertain usage: Starter to try it, Growth for most projects, Scale for heavy use. Point to [pricing](/pricing) for monthly plans.
* Tell the buyer to pay with the **email address of their Social Fetch account**, or the one they'll sign up with. That's how the credits find them.
* After purchase, send them to [create an API key](https://app.socialfetch.dev/api-keys) or [connect MCP](/docs/integrations/mcp).
* Working in the person's browser instead of a chat? Our site and dashboard offer [WebMCP tools](/docs/integrations/webmcp): `get_pricing` for live prices and `start_credit_purchase` to open checkout.

## FAQ

**Which assistants can sell Social Fetch?**
Any assistant connected to Stripe agentic commerce that we've enabled. If yours shows Social Fetch in its shopping results, you can buy there.

**Is it more expensive than buying on the website?**
No. Same packs, same prices.

**I bought credits but can't see them.**
Check you're signed in with the email you paid with. If it's different, reply to our confirmation email or [contact support](https://app.socialfetch.dev/support).