docs: add agent onboarding page

[lukas-bekr]

Summary

• Adds an agent onboarding page at /platform/integrations/agent-onboarding
• Entry point for developers and AI agents connecting to Apify
• Covers all integration methods: MCP server, Agent Skills, API client, CLI, REST API
• Includes FAQ section optimized for agent consumption
• API quick reference table with key endpoints including the sync run-sync-get-dataset-items shortcut

Relationship to #2367

This is an alternative take on the same problem as #2367 by @nicoleolender. Key differences:

This PR	#2367
Includes Agent Skills section	Missing skills coverage
FAQ section (optimized for agent parsing)	No FAQ
apify-client vs apify naming trap warning	Not covered
MCP Configurator link (mcp.apify.com)	Not covered
Lighter on CLI/API code examples	More detailed curl examples

Both PRs share the same signpost/hub-and-spoke philosophy - link out to detailed docs rather than duplicate content. The best version is probably a merge of both. Happy to consolidate into one.

Structure

1. Core concepts intro (Actors, Datasets, API)
2. Prerequisites (account, token, free exploration tip)
3. Integration methods (MCP > Skills > API client > CLI > REST API)
4. Documentation access for agents (.md URLs, Accept: text/markdown, MCP tools)
5. FAQ (5 questions covering common agent confusion points)
6. Useful resources (links to CLI, API, client libs, storage, academy)

Context

• Discussion: #proj-agent-experience Slack channel
• Research: State of Docs 2026 findings on FAQ format for agent consumption
• Companion PR: feat: add agent-onboarding skill agent-skills#30 (the SKILL.md skill itself)

Test plan

• Page renders correctly in Docusaurus preview (npm start)
• All internal links resolve (no broken links)
• Tabs component works for JS/Python code examples
• Admonitions render with correct titles
• npm run lint:md passes

🤖 Generated with Claude Code

---

Note

Low Risk
Low risk documentation-only change that adds a new onboarding page; the main risk is broken links or incorrect setup instructions for MCP/Skills/API usage.

Overview
Adds a new platform/integrations/agent-onboarding doc page that serves as an entry point for connecting AI agents/apps to Apify.

The page documents multiple integration paths (remote/local MCP server setup, Agent Skills install, JS/Python apify-client examples, CLI usage, and a REST API quick-reference including run-sync-get-dataset-items), plus guidance on programmatic docs access and an agent-friendly FAQ/resources section.

^{Written by Cursor Bugbot for commit b19a982. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is kicking off a free cloud agent to fix this issue. This run is complimentary, but you can enable autofix for all future PRs in the Cursor dashboard.}

Comment @cursor review or bugbot run to trigger another review on this PR

[cursor]

Slug format causes incorrect URL path resolution

High Severity

The slug value platform/integrations/agent-onboarding is missing a leading / and incorrectly includes the platform/ prefix. Every other doc in this directory uses an absolute slug pattern like /integrations/crewai. Since the Docusaurus docs plugin already sets routeBasePath: 'platform', this relative slug gets resolved against the file's directory, producing a deeply nested and incorrect URL instead of the intended /platform/integrations/agent-onboarding. The correct slug is /integrations/agent-onboarding.

 

[cursor]

Bugbot Autofix determined this is a false positive.

The file mentioned in the bug report (agent-onboarding.md with slug 'platform/integrations/agent-onboarding') does not exist; the actual file is ai-agents.md with correct slug '/integrations/ai-agents', and git history shows all versions always had correct slug format with leading slash.

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}