docs(mcp): Add Skyfire agentic payments and hosted server benefits docs (#2236)

## Summary
This PR adds documentation for two new features in the Apify MCP server:
1. Highlights the benefits of using the hosted MCP server over local
stdio setup
2. Introduces the new Skyfire integration for agentic payments

## Key Changes
- **Hosted server tip**: Added a prominent tip section explaining that
the hosted Apify MCP server at `https://mcp.apify.com` supports output
schema inference for structured Actor results, which is not available in
local stdio mode
- **Skyfire agentic payments section**: Added comprehensive
documentation covering:
- Overview of how Skyfire enables autonomous payments for Actor runs
without requiring Apify API tokens
- Prerequisites (Skyfire account with funded wallet, compatible MCP
client)
- Setup instructions with example configuration showing both Skyfire and
Apify servers
- Step-by-step explanation of the payment flow (discovery → PAY token
creation → Actor execution → results)
  - Links to related documentation and blog post

## Implementation Details
- The tip about hosted server benefits is placed early in the transport
section to guide users toward the recommended setup
- Skyfire integration documentation is positioned as a new top-level
section before the Telemetry section
- Configuration examples use standard JSON format for easy copy-paste
into MCP client configs
- Documentation includes clear prerequisites and step-by-step workflow
explanation to help users understand the autonomous payment flow

https://claude.ai/code/session_01URvA6cQdYqwCF1s1PWNL6v

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Documentation-only changes; no runtime behavior, security, or billing
logic is modified.
> 
> **Overview**
> Adds a new *hosted server tip* to the MCP quick-start docs explaining
that `https://mcp.apify.com` provides **output schema inference**
(field-level typed output schemas) that is not available in local stdio
mode.
> 
> Introduces a new **"Agentic payments with Skyfire"** section
describing tokenless Actor execution via Skyfire PAY tokens, including
prerequisites, multi-server client configuration (using
`?payment=skyfire`), and the end-to-end payment flow (discover Actor →
create PAY token → pass `skyfire-pay-id` → run).
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
55c85ba. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Michał Olender <92638966+TC-MO@users.noreply.github.com>

Author: 3 people

sources/platform/integrations/ai/mcp.md

@@ -15,7 +15,7 @@ import TabItem from '@theme/TabItem';
 The Apify's MCP server ([mcp.apify.com](https://mcp.apify.com)) allows AI applications and agents to interact with the Apify platform
 using [Model Context Protocol](https://modelcontextprotocol.io/docs/getting-started/intro). The server enables AI agents to
 discover and run Actors from [Apify Store](https://apify.com/store), access storages and results,
-and enabled AI coding assistants to access Apify documentation and tutorials.
+and enables AI coding assistants to access Apify documentation and tutorials.
 
 ![Apify MCP Server](../../images/apify_mcp_server.png)
 
@@ -37,6 +37,12 @@ Server-Sent Events (SSE) transport will be removed on April 1, 2026. The Apify M
 
 :::
 
+:::tip Structured output schemas
+
+The hosted Apify MCP server at `https://mcp.apify.com` supports _output schema inference_ for structured Actor results. Actor tools automatically include inferred output schemas with field-level type information. This helps AI agents understand the expected result structure before calling an Actor. The local stdio server does not support this feature.
+
+:::
+
 ### Streamable HTTP with OAuth (recommended)
 
 Provide the server URL `https://mcp.apify.com`. You will be redirected to your browser to sign in to your Apify account and approve the connection.
@@ -278,7 +284,7 @@ Use the UI configurator `https://mcp.apify.com/` to select your tools visually,
 | Tool name | Category | Enabled by default | Description |
 | :--- | :--- | :--- | :--- |
 | `search-actors` | actors | ✅ | Search for Actors in Apify Store |
-| `fetch-actor-details` | actors | ✅ | Retrieve detailed information about a specific Actor |
+| `fetch-actor-details` | actors | ✅ | Retrieve detailed information about a specific Actor, including its input and output schema, README, and pricing |
 | `call-actor`* | actors | ❔ | Call an Actor and get its run results |
 | [`apify/rag-web-browser`](https://apify.com/apify/rag-web-browser) | Actor | ✅ | Browse and extract web data |
 | `search-apify-docs` | docs | ✅ | Search the Apify documentation for relevant pages |
@@ -320,6 +326,48 @@ For a detailed overview of client support for dynamic discovery, see the [MCP cl
 
 :::
 
+## Agentic payments with Skyfire
+
+The Apify MCP server integrates with [Skyfire](https://www.skyfire.xyz/) to enable _agentic payments_. This allows AI agents to autonomously pay for Actor runs without requiring an Apify API token. Instead of authenticating with an Apify token, the agent uses Skyfire _PAY tokens_ to cover billing for each tool call.
+
+### Prerequisites
+
+- _Skyfire account_ - Sign up for a [Skyfire account](https://www.skyfire.xyz/) and fund your wallet.
+- _MCP client with multi-server support_ - An MCP client that supports multiple servers, such as Claude Desktop or VS Code.
+
+### Setup
+
+Configure both the Skyfire MCP server and the Apify MCP server in your client. Enable payment mode by adding the `payment=skyfire` query parameter to the Apify server URL:
+
+```json
+{
+  "mcpServers": {
+    "skyfire": {
+      "url": "https://api.skyfire.xyz/mcp/sse",
+      "headers": {
+        "skyfire-api-key": "<YOUR_SKYFIRE_API_KEY>"
+      }
+    },
+    "apify": {
+      "url": "https://mcp.apify.com?payment=skyfire"
+    }
+  }
+}
+```
+
+Replace `<YOUR_SKYFIRE_API_KEY>` with your API key from your [Skyfire dashboard](https://www.skyfire.xyz/).
+
+### How it works
+
+When Skyfire payment mode is enabled, the agent handles the full payment flow autonomously:
+
+1. The agent discovers relevant Actors via `search-actors` or `fetch-actor-details` (these remain free).
+1. Before executing an Actor, the agent creates a PAY token using the `create-pay-token` tool from the Skyfire MCP server (minimum $5.00 USD).
+1. The agent passes the PAY token in the `skyfire-pay-id` input property when calling the Actor tool.
+1. The Actor returns results as usual. Unused funds on the token remain available for future runs or return upon expiration.
+
+To learn more, see the [Skyfire integration documentation](/platform/integrations/skyfire) and the [Agentic Payments with Skyfire](https://blog.apify.com/agentic-payments-skyfire/) blog post.
+
 ## Telemetry
 
 The MCP server collects telemetry data about tool calls and MCP clients to help Apify understand usage patterns and improve the service.