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

# November 16, 2026

> Python and Go SDKs and CLI support, and agent payments in preview for TypeScript, Python and Go.

## Python and Go SDKs

SolvaPay now has SDKs for Python and Go, next to the TypeScript SDK. Each covers the server side:

* Make a function paid: each call is checked against the customer's plan and billed when it succeeds.
* Paid and free MCP tools, with SolvaPay sign-in, the built-in `account` and `activate_plan` tools,
  and the checkout widget on MCP Apps hosts.
* Webhook verification.
* The full SolvaPay API, generated from the same spec as the TypeScript types.

```bash theme={null}
pip install solvapay                               # Python 3.10+
go get github.com/solvapay/solvapay-sdk/go@latest  # Go 1.26+
```

The paywall, its messages, the `account` tool's answers and webhook verification behave the same
in all three SDKs. A shared conformance suite checks the Python and Go SDKs against the TypeScript
SDK on every change. Each SDK has its own version line, starting at 0.1.0 (Go tags are
`go/vX.Y.Z`), so the numbers don't line up across languages.

Python and Go have no frontend packages, but the React checkout components work with a Python or Go
backend: see React web checkout for [Python](https://docs.solvapay.com/sdks/python/guides/react-web-checkout.md) and
[Go](https://docs.solvapay.com/sdks/go/guides/react-web-checkout.md).

## The CLI for Python and Go

The SolvaPay CLI now sets up Python and Go projects too. It runs on Node.js 22 or later:

* `npx solvapay init` detects the language from `go.mod`, `uv.lock`, `poetry.lock`,
  `pyproject.toml`, `requirements.txt` or `package.json`. It signs you in, writes
  `SOLVAPAY_SECRET_KEY` and `SOLVAPAY_PRODUCT_REF` to `.env`, and adds the SDK pinned exactly with
  `uv add`, `poetry add` or `go get`. For plain pip it prints the install command. When the folder
  has files for two languages, or none, pass `--language ts|python|go`.
* `npm create solvapay@latest my-server -- --type mcp --language python` (or `go`) scaffolds a paid
  MCP server with one paid tool, one free tool, tests and a Dockerfile.
* `npx solvapay doctor` checks that the SDK is the newest release in every language the project
  uses, and prints the upgrade command.
* `npx solvapay verify <server url>` checks a running MCP server in any language.

In a folder with no project files, `init --yes` no longer creates a `package.json` on its own. Pass
`--language ts` for that. See [CLI setup](https://docs.solvapay.com/sdks/typescript/setup/cli.md).

See the [Python SDK](https://docs.solvapay.com/sdks/python/intro.md) and the [Go SDK](https://docs.solvapay.com/sdks/go/intro.md).

## Agent payments (preview)

SolvaPay agents can pay for your API or MCP tools per call. Each paid call is authorized with
SolvaPay before it runs and completed at its actual cost. The TypeScript (`@solvapay/agents`),
Python (`solvapay[agents]`) and Go (`github.com/solvapay/solvapay-sdk/go/agents`) SDKs support
it.

Agent payments are in preview and have to be turned on for your account. See agent payments for
[TypeScript](https://docs.solvapay.com/sdks/typescript/guides/agents.md), [Python](https://docs.solvapay.com/sdks/python/guides/agents.md) and
[Go](https://docs.solvapay.com/sdks/go/guides/agents.md).


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