Integration

Plisio integration

Plisio is a cryptocurrency payment gateway for online shops. Every Plisio call is an HTTP GET, including the two that act: creating an invoice and creating a deposit address. Create payment invoices priced in a cryptocurrency or in a fiat currency, read an invoice and its payment status, list and read every operation of the account (invoices, incoming payments, withdrawals), read balances per cryptocurrency, list the supported cryptocurrencies with their rates, estimate network fees and Plisio commission, read the fee plans, read the shop's settings, and with white-label processing create and list permanent deposit addresses bound to your own user ids. Left out: withdrawals and mass withdrawals (they send funds irreversibly and the vendor's pages disagree on their currency parameter), the crypto exchange routes (their responses are not documented consistently), the hosted invoice page's payer actions (switching currency, entering the payer email), the payment button redirect and the Telegram bot hook. Authentication is the shop's Secret Key (API settings of the shop), sent as the api_key query parameter; leave the shop's Limit Access by IP address field empty (a restricted IP list refuses calls from other addresses), and answers 401 when the key is wrong or the shop domain is not verified.

Connect Plisio How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Plisio.Built from the 12 Plisio tools below, on the connection you add once.

What you can do with Plisio

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Deposit address, 2 operations

create_deposit_addressCreate deposit addressGETCreate a user's permanent deposit address in one cryptocurrency (a GET call that still creates it). Funds sent there are credited to your account for that uid. Needs white-label processing. One psys_cid per call.
list_deposit_addressesList deposit addressesGETList the permanent deposit addresses of the shop, filtered by your user id and cryptocurrencies. White-label processing must be enabled. Page with page and limit.

Invoice, 2 operations

create_invoiceCreate invoiceGETCreate a real payment invoice (a GET call that still creates it). The payer pays at invoice_url; updates go to callback_url. order_number must be unique in your store. Price with amount (crypto) or source_currency plus source_amount (fiat).
get_invoiceGet invoiceGETRead one invoice with its amounts, received and remaining amounts, payment address, status, block explorer links, the shop's public details and the selected cryptocurrency. Pass the txn_id from create_invoice or an invoice id from list_operations.

Operation, 2 operations

get_operationGet operationGETRead one operation (invoice, incoming payment, withdrawal) with its amounts, fees, commission, status and blockchain transactions. Pass an id from list_operations.
list_operationsList operationsGETList the account's operations (invoices, incoming payments, withdrawals) filtered by type, status, currency, shop or a text search. Page with page and limit; data._meta gives the totals.

Balance, 1 operation

get_balanceGet balanceGETRead the account balance in one cryptocurrency. Pass its Plisio ID (cid from list_currencies) as psys_cid.

Commission, 1 operation

estimate_commissionEstimate commissionGETEstimate the network fee and the Plisio commission of a transfer to one or several addresses, before sending it. Pass the cryptocurrency, the addresses and the amounts (comma-separated for several).

Currency, 1 operation

list_currenciesList currenciesGETList the cryptocurrencies Plisio supports, with each one's rate and price in USD and in the fiat currency you pass, minimum invoice amount, commission and maintenance state.

Fee, 1 operation

estimate_feeEstimate feeGETEstimate the network fee of a transfer to one or several addresses for a fee plan. Pass the cryptocurrency, the addresses and the amounts (comma-separated for several).

Fee plan, 1 operation

get_fee_plansGet fee plansGETRead the fee plans (normal and priority) of one cryptocurrency with their fee values. The extra fields depend on the coin: blocks to confirm, or gas limit and gas price.

Shop, 1 operation

get_shopGet shopGETRead the shop the Secret Key belongs to: name, site link, who pays the commission, whether white-label processing is enabled and whether the domain is verified.

Use Plisio from Claude Code, Cursor or Codex

Connect Plisio in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Plisio operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Plisio

Create your workspace
Sign up free. Nothing to install.
Connect Plisio once
Add your Plisio connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.