Restructure integrations docs to mirror apify.com/integrations and add tier ranking

[marcel-rbro]

Background

Restructure the sources/platform/integrations/ section so that:

• Categories mirror the apify.com/integrations landing page, where reasonable.
• The MCP server moves into Built-in integrations alongside API, Actors, and Webhooks.
• Each integration's sidebar_position encodes a tier (1 = S, 2 = Mid, 3 = Other) so the sidebar surfaces the most popular integrations first within each category. Within a tier, items order alphabetically.

Internal context: prioritization came from Lukas Bekr; the tier list below reflects his ranking.

Tier ranking

• S-tier (sidebar_position: 1) — all built-in (API, Actors, Webhooks, MCP), plus n8n, Make, Zapier, OpenClaw, Gumloop, Google ADK, LangChain, OpenAI Agents SDK, Vercel AI SDK, Airtable, Snowflake, Manus, x402, Pinecone, GitHub
• Mid (sidebar_position: 2) — Dify, Workato, Windmill, Bubble, IFTTT, Lindy, Amazon Bedrock, CrewAI, Keboola, Gmail, Telegram, Slack, Upsonic
• Other (sidebar_position: 3) — everything else

Proposed top-level folders

Folder	Maps to LP category	Notes
built-in/	Built-in platform integrations	API, Actors, Webhooks, MCP (moved from ai/mcp/)
workflow-automation/	Workflow automation	was workflows-and-notifications/, narrowed
ai-assistants/	AI assistants	new
ai-sdks-frameworks/	AI SDKs & frameworks	new (split from ai/)
collaboration/	Collaboration	Gmail, Slack, Drive
data-pipelines/	ELT & data pipelines	was data-storage/, narrowed
vector-db-storage/	Vector DB & storage	new
developer-tools/	Developer tools	GitHub
payments/	Payments	x402, Skyfire
other/	(catch-all)	Bubble, Dify, Telegram

LP categories without docs (Coding agents & IDEs, App builders, GTM tools, MCP gateways, iPaaS, Productivity) are out of scope here.

URLs

All integration pages use a flat slug (slug: /integrations/<name>). Folder reorganization does not change URLs - no redirects required.

Out of scope

• Writing new pages for empty LP categories.
• Theme or component changes.
• Changes to apify.com/integrations itself.

Implementation

PR will follow this issue.

[bastizol-wq]

Re: “Restructure integrations docs to mirror apify.com/integrations and add tier ranking”. When agents call tools, the brittle part is usually the tool boundary (auth/hosts/inputs).

A quick pre-flight checklist: enforce HTTPS, allowlist hosts, require auth where expected, flag destructive ops, and emit a structured receipt.

ATCP sits in front of tool execution: evaluate first, then decide whether the agent can call.

If you’re already on OpenAPI, starting with a tiny evaluate endpoint + receipt logging is a low-effort step.