# How to connect Plisio to OpenClaw (paste one key, 12 tools) > Connect Plisio to OpenClaw with ClawLink: paste your Plisio key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/plisio The usual route to Plisio access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Plisio setup: install one ClawHub skill, connect Plisio in the browser, and OpenClaw can call real Plisio actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to Plisio. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Plisio** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect plisio # connect Plisio (browser OAuth) npx -y @useclawlink/cli actions plisio # list available actions npx -y @useclawlink/cli run plisio --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect Plisio in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Plisio API key once. Verify the connection by asking OpenClaw: > Use Plisio to estimate fee and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Plisio is connected in the dashboard, that agent calls the same 12 Plisio tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## Plisio MCP for OpenClaw Looking for a Plisio MCP server for OpenClaw? ClawLink connects Plisio to OpenClaw and exposes 12 Plisio tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes Plisio integration](https://claw-link.dev/hermes/plisio) works the same way. ## What the OpenClaw Plisio integration can do 12 Plisio tools are ready for OpenClaw once the account is connected. ### All 12 Plisio tools for OpenClaw | Tool | What it does | |---|---| | **Estimate fee** `plisio_estimate_fee` | Estimate network fee for a withdrawal transaction to specific address(es) | | **Get balance by currency** `plisio_get_balance_by_currency` | Get the balance for a specific cryptocurrency in your Plisio account | | **Get commission** `plisio_get_commission` | Estimate the total cost including network fee and Plisio commission for a transaction | | **Get currency rate** `plisio_get_currency_rate` | Retrieve list of supported cryptocurrencies with current rates filtered by fiat currency | | **Get fee plans** `plisio_get_fee_plans` | Retrieve available fee plans for a given cryptocurrency | | **Get fee plans2** `plisio_get_fee_plans2` | Get available fee plans for a specific cryptocurrency | | **Get invoice** `plisio_get_invoice` | Retrieve detailed information about a specific invoice by its ID | | **Get invoice email** `plisio_get_invoice_email` | Retrieve invoice details by email ID | | **Get shop** `plisio_get_shop` | Retrieve shop information by API key | | **Get transactions** `plisio_get_transactions` | Retrieve a list of transactions and invoices | | **List currencies** `plisio_list_currencies` | Retrieve a list of supported cryptocurrencies with their rates and information | | **Create invoice** `plisio_create_invoice` | Create a new cryptocurrency payment invoice with Plisio | ## Example prompts **Estimate Fee** > Use Plisio to estimate fee and walk me through the result in plain English. **Get Balance By Currency** > Pull the relevant data from Plisio, summarize it in plain English, and point out anything that needs attention. **Get Commission** > Pull the relevant data from Plisio, summarize it in plain English, and point out anything that needs attention. **Get Currency Rate** > Pull the relevant data from Plisio, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Plisio working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Plisio API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Plisio account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Plisio. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right Plisio actions to the runtime in a format your agent can reliably use. | 12 tools for Plisio are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Plisio to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Plisio in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Plisio key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the Plisio skill but can't call the tools The ClawHub skill teaches OpenClaw about Plisio, but the calls run through the ClawLink plugin and your connected account. Make sure Plisio is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect Plisio from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling Plisio tools Plisio tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Plisio call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### Plisio returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for Plisio has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Plisio integration? Yes. ClawLink is the fastest way to connect OpenClaw to Plisio: link your Plisio account once in the browser and OpenClaw can call the Plisio API through 12 ready-made tools — no custom code or token handling. ### How do I add Plisio to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Plisio skill from ClawHub, then you click Connect in the dashboard to authorize Plisio. OpenClaw calls the tools from the next message — no config files, and the Plisio key you paste is stored server-side instead of in your environment. ### How long does it take to connect Plisio to OpenClaw? About two minutes. Sign in, click Connect next to Plisio in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Plisio up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Plisio working from chat. ### OpenClaw installed the Plisio skill but can't call the tools The ClawHub skill teaches OpenClaw about Plisio, but the calls run through the ClawLink plugin and your connected account. Make sure Plisio is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Stripe tools](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Zoho Books](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [OpenClaw Ramp integration](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts