> ## Documentation Index
> Fetch the complete documentation index at: https://docs.solvapay.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> SolvaPay quick facts:
> - REST API base URL: https://api.solvapay.com. All public endpoints are under /v1/sdk/ (for example GET https://api.solvapay.com/v1/sdk/products). Sandbox and production share this URL.
> - Auth: send a secret key as `Authorization: Bearer <secret key>` (the REST API also accepts `X-API-Key: <secret key>`).
> - Secret key prefixes: `sk_sandbox_` (sandbox, test payments) and `sk_live_` (production). The prefix selects the environment.
> - Get keys in SolvaPay Console (https://app.solvapay.com) > Developers > API Keys. Use a sandbox key while building.
> - Admin MCP Server: https://mcp.solvapay.com/mcp (Streamable HTTP). Connect with OAuth: add the URL and sign in with the SolvaPay account; no API key needed. OAuth sessions use the live account; for sandbox data or headless clients, send `Authorization: Bearer <secret key>` (X-API-Key is ignored).
> - Install the SolvaPay agent skills: `npx skills add https://solvapay.com` (skills CLI older than 1.5.7: `npx skills add solvapay/skills`).
> - TypeScript SDK setup: `npx solvapay@latest init`. The SDK reads SOLVAPAY_SECRET_KEY and defaults to https://api.solvapay.com.
> - Plans take an options[] array (billingCycle, charge, limit, ...). Retired plan fields price, freeUnits and billingCycle are rejected.
> - Step-by-step from zero to a first paid call: Managed MCP https://docs.solvapay.com/build/managed-mcp.md, TypeScript SDK https://docs.solvapay.com/build/typescript-sdk.md, agent skill https://docs.solvapay.com/build/agent-skill.md.
> - Details: https://docs.solvapay.com/api-reference/authentication.md. OpenAPI spec: https://docs.solvapay.com/api-reference/openapi.json.

# What each MCP host can render

> Where SolvaPay checkout, account pages and MCP UIs appear in Claude, Claude Code, ChatGPT and Grok Bot.

Every host can show text and links returned by an MCP server. They differ in whether the server can draw its own interface inside the chat and where the checkout form appears. When a host cannot show the form inline, SolvaPay returns a link to a hosted page and the host opens it in a built-in browser or hands it to the system browser.

## Capability matrix

| | [Claude](https://docs.solvapay.com/mcp-hosts/claude.md) | [Claude Code (terminal)](https://docs.solvapay.com/mcp-hosts/claude-code.md#terminal) | [Claude Code (desktop)](https://docs.solvapay.com/mcp-hosts/claude-code.md#desktop-app) | [ChatGPT](https://docs.solvapay.com/mcp-hosts/chatgpt.md) | [Grok Bot](https://docs.solvapay.com/mcp-hosts/grok-bot.md) |
| - | - | - | - | - | - |
| **Text and links**  Plain responses with clickable URLs | Supported | Supported | Supported | Supported | Supported |
| **Render MCP UIs**  Server-defined interface shown inside the chat | Renders inline | Text and links only | Text and links only | Renders inline | Text and links only |
| **Where the payment form appears**  Same SolvaPay checkout, placed where the host allows | Hosted page, in Claude's built-in browser | Hosted page, in the system browser | Hosted page, in the app's built-in browser | Inline in the chat | Hosted page, in the system browser |
| **Account pages**  Plan, usage and billing history, always hosted by SolvaPay | Hosted page, in Claude's built-in browser | Hosted page, in the system browser | Hosted page, in the app's built-in browser | Hosted page, in the system browser | Hosted page, in the system browser |

> [!NOTE]
>
> Every host can complete a payment. "Inline in the chat" means the form is drawn inside the conversation by the MCP server. "Hosted page" means the server returns a link to a SolvaPay-hosted page, and the host decides which browser opens it.

## How the fallback works

The host decides what to show. Your MCP server sends the same response to every host.

1. Every SolvaPay tool response includes a complete text answer. Any checkout or account action in it is a plain `https://` link.
2. The SolvaPay `account` tool also declares an MCP UI. Hosts that support MCP Apps, such as Claude and ChatGPT, render it inside the chat. Other hosts ignore it and show the text.
3. When a paid tool is blocked, the response text states the limit and includes a link to hosted checkout.
4. If a host renders the MCP UI but does not allow the card form inside it, the UI opens hosted checkout instead.
5. The host opens the link. Claude and Claude Code desktop use their built-in browser. Claude Code in the terminal and Grok Bot hand it to the system browser.
6. After payment, return to the chat. The next call to the paid tool runs.

To build the MCP UI yourself, see the [MCP App integration guide](https://docs.solvapay.com/sdks/typescript/guides/mcp-app.md). For the hosted pages themselves, see [Hosted pages](https://docs.solvapay.com/no-code-mcp/hosted-pages.md).

## Hosts

> [card] [Claude](https://docs.solvapay.com/mcp-hosts/claude.md)
>
> Renders MCP UIs inline. Checkout opens as a hosted page in Claude's built-in browser.

> [card] [Claude Code](https://docs.solvapay.com/mcp-hosts/claude-code.md)
>
> Text and links only. Checkout opens in the system browser or the desktop app's built-in browser.

> [card] [ChatGPT](https://docs.solvapay.com/mcp-hosts/chatgpt.md)
>
> Renders MCP UIs and the payment form inline in the chat.

> [card] [Grok Bot](https://docs.solvapay.com/mcp-hosts/grok-bot.md)
>
> Text and links only. Checkout opens in the system browser.

## Other MCP hosts

SolvaPay works in any MCP host that shows text and links. Until we have tested a host, assume the hosted-page path: checkout and account pages open from a link in the tool response.

> [!WARNING]
>
> The matrix reflects what we tested on 2026-09-30. Host capabilities change often and without notice, so a cell may be out of date by the time you read it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.