> ## 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.

# SolvaPay in Claude Code

> How SolvaPay checkout and account pages work when your MCP server runs in Claude Code, in the terminal and in the desktop app.

Claude Code shows text and links only. It does not render MCP UIs, so checkout and account pages always open as SolvaPay-hosted pages. In the terminal, the link opens in the system browser. In the desktop app, it opens in the app's built-in browser.

## What works

| | Terminal | Desktop app |
| - | - | - |
| Text and links | Supported | Supported |
| MCP UIs | Text and links only | Text and links only |
| Payment form | Hosted page, in the system browser | Hosted page, in the app's built-in browser |
| Account pages | Hosted page, in the system browser | Hosted page, in the app's built-in browser |

## Checkout

When a paid tool is blocked, the response text states the limit and includes a link to hosted checkout. The customer opens the link, pays, and returns to Claude Code. The next call to the paid tool runs.

## Account pages

Ask the assistant to manage the account. The `account` tool returns the current plan, usage and a link to the SolvaPay-hosted account page.

## MCP UIs

Claude Code ignores MCP UIs. Every SolvaPay response already contains a complete text answer, so nothing is lost.

## Terminal

The terminal hands hosted links to your system browser. Add the server from your shell, not inside a `claude` session:

```bash theme={null}
claude mcp add --transport http my-server https://your-mcp-server.example.com/mcp
```

Then start `claude` and run `/mcp` to authenticate. See Claude Code's [MCP quickstart](https://code.claude.com/docs/en/mcp-quickstart) for scopes and config files.

## Desktop app

The desktop app shows the same text responses and opens hosted links in its built-in browser. Add the server with the same Claude Code MCP setup as the terminal.

## Known limitations

* There is no inline checkout. Card entry always happens on the hosted page.
* Hosted checkout links expire after 15 minutes. Ask the assistant for a new link if one has expired.

Last tested: 2026-09-30


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