ClawLink

How to connect Skyfire to OpenClaw

Connect Skyfire to OpenClaw with ClawLink: paste your Skyfire key once and 16 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
OpenClaw
OpenClaw
ClawLink
ClawLink
Skyfire
Skyfire
SkyfireAPI KEYMCP

Skyfire enables AI agents to autonomously transact and pay for services, creating a seamless payment infrastructure for AI applications.. Once connected, OpenClaw can read and act on Skyfire from chat — pairing, token refresh, and tool wiring handled for you.

16 tools

The usual route to Skyfire 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 Skyfire setup: install one ClawHub skill, connect Skyfire in the browser, and OpenClaw can call real Skyfire 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 Skyfire.

  1. 1

    Install the plugin

    Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:

    openclaw plugins install clawhub:clawlink-plugin
  2. 2

    Connect Skyfire

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask OpenClaw: "What can you do with Skyfire?"

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:

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 Skyfire in the ClawLink dashboard — paste your Skyfire API key once.

Verify the connection by asking OpenClaw:

Pull the relevant data from Skyfire, summarize it in plain English, and point out anything that needs attention.

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:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Skyfire is connected in the dashboard, that agent calls the same 16 Skyfire tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Skyfire MCP for OpenClaw

Looking for a Skyfire MCP server for OpenClaw? ClawLink connects Skyfire to OpenClaw and exposes 16 Skyfire tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Skyfire integration works the same way.

What the OpenClaw Skyfire integration can do

16 Skyfire tools are ready for OpenClaw once the account is connected.

All 16 Skyfire tools for OpenClaw

ToolWhat it does
Get all service tags skyfire_get_all_service_tagsFetch all service tags to discover filtering options
Get buyer wallet balance skyfire_get_buyer_wallet_balanceRetrieve buyer wallet balance
Get directory service by ID skyfire_get_directory_service_by_idGet full details for a specific service in the Skyfire directory by its ID
Get service skyfire_get_serviceGet full details for one service
Get services by agent skyfire_get_services_by_agentBrowse all services from one seller agent
Get services by tags skyfire_get_services_by_tagsFilter services by tags to find exactly what you need
Get token charges skyfire_get_token_chargesAudit charges for a specific token
Introspect token skyfire_introspect_tokenCheck if a token is still valid before calling a seller service
List agent seller services skyfire_list_agent_seller_servicesList all services registered by the authenticated seller agent
List buyer tokens skyfire_list_buyer_tokensInspect buyer tokens for observability
List directory services skyfire_list_directory_servicesBrowse Skyfire's service directory to obtain sellerServiceId for token creation
Charge token skyfire_charge_tokenCharge a buyer's token (seller-side operation)
Create kya pay token skyfire_create_kya_pay_tokenIssue a Skyfire KYA+PAY token (POST /api/v1/tokens with type=kya+pay)
Create kya token skyfire_create_kya_tokenIssue a Skyfire KYA token (POST /api/v1/tokens with type=kya)
Create pay token skyfire_create_pay_tokenIssue a Skyfire PAY token (POST /api/v1/tokens with type=pay)
Set agent source ips skyfire_set_agent_source_ipsRegister IP addresses as sources for Agent requests (PUT /api/v1/agents/source-ips)

Try it: find the Skyfire tool you need

Browse the 16 Skyfire tools

Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Skyfire, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Skyfire, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Skyfire, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Skyfire, summarize it in plain English, and point out anything that needs attention.

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 Skyfire working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Skyfire API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Skyfire account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Skyfire.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Skyfire actions to the runtime in a format your agent can reliably use.16 tools for Skyfire are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Skyfire 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 Skyfire in the browser, and the 16 tools above work from chat. There is no SDK and no config file, and the Skyfire key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

OpenClaw installed the Skyfire skill but can't call the tools

The ClawHub skill teaches OpenClaw about Skyfire, but the calls run through the ClawLink plugin and your connected account. Make sure Skyfire 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 Skyfire 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 Skyfire tools

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

Skyfire 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 Skyfire has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a OpenClaw Skyfire integration?

Yes. ClawLink is the fastest way to connect OpenClaw to Skyfire: link your Skyfire account once in the browser and OpenClaw can call the Skyfire API through 16 ready-made tools — no custom code or token handling.

How do I add Skyfire to OpenClaw with ClawLink?

Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Skyfire skill from ClawHub, then you click Connect in the dashboard to authorize Skyfire. OpenClaw calls the tools from the next message — no config files, and the Skyfire key you paste is stored server-side instead of in your environment.

How long does it take to connect Skyfire to OpenClaw?

About two minutes. Sign in, click Connect next to Skyfire in the dashboard, authenticate, and OpenClaw can use it from the next chat message.

Why use ClawLink instead of wiring Skyfire 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 Skyfire working from chat.

OpenClaw installed the Skyfire skill but can't call the tools

The ClawHub skill teaches OpenClaw about Skyfire, but the calls run through the ClawLink plugin and your connected account. Make sure Skyfire 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.