> ## 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 Grok Bot

> How SolvaPay checkout and account pages work when your MCP server runs in Grok Bot, the xAI agent app.

[Grok Bot](https://x.ai/bot) shows text and links only. It does not render MCP UIs, so checkout and account pages open as SolvaPay-hosted pages in the system browser.

## What works

* Text and links: supported.
* MCP UIs: text and links only.
* Payment form: hosted page, in the system browser.
* Account pages: hosted page, in the system 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 in the system browser, pays, and returns to Grok Bot. The next call to the paid tool runs.

## Account pages

Ask the bot to manage the account. The `account` tool returns the current plan, usage and a link to the SolvaPay-hosted account page, which opens in the system browser.

## MCP UIs

Grok Bot ignores MCP UIs and uses only the markdown text of a response. Every SolvaPay response already contains a complete text answer with plain `https://` links, so nothing is lost.

## Connect your MCP server

Grok Bot has no connector form. Ask the bot to add the server in chat:

```text theme={null}
Add this MCP server: https://your-mcp-server.example.com/mcp
```

The bot repeats the URL and asks you to confirm before it saves the connector. Tools are available from the next message.

The server must be a public HTTPS URL using Streamable HTTP or SSE. Grok Bot runs on its own computer in the cloud, so it cannot reach `localhost`. This is separate from adding a connector at grok.com, which is Grok chat.

## Known limitations

* There is no inline checkout. Card entry always happens on the hosted page.
* Hosted checkout links expire after 15 minutes. Ask the bot 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.