Refunds, subscription changes and invoicing are write operations against live revenue, and the separate sandbox endpoint exists precisely so an agent workflow can be proven before it is pointed at production. Swapping the URL is the only difference between the two, which makes the promotion step trivially easy — and trivially easy to do by accident, so keep the two configurations distinct.
The hosted MCP surface for Subotiz, a subscription growth and merchant-of-record platform aimed at AI products, SaaS and digital businesses. Connecting it lets an agent handle the revenue operations side — pricing, subscriptions, transactions, refunds and invoices — rather than only reporting on them.
Product pricing managed, subscriptions handled, transactions and refunds processed, and invoices issued — the revenue operations Subotiz covers as a merchant of record, reachable from an agent. Support spans over 180 countries and 150+ currencies, with usage-based billing, global payments and tax compliance handled by the platform rather than by your own billing code. A sandbox environment mirrors production so a flow can be exercised before it moves money.
A valid Subotiz access token, which is your Subotiz API key, sent as `Authorization: Bearer` — no other request headers are needed against the official hosted service. A host that supports Streamable HTTP MCP, such as VS Code 1.101+, Claude Desktop, Cursor or Trae. Two endpoints: `https://api.sandbox.subotiz.com/mcp` for sandbox and `https://api.subotiz.com/mcp` for production. The authentication guide in Subotiz's documentation covers creating the key.