How to connect Rize to OpenClaw
Connect Rize to OpenClaw with ClawLink: paste your Rize key once and 8 tools work from chat. No MCP server to run, nothing stored on your machine.
RizeAPI KEYMCPRize is an AI-powered time tracking and productivity tool that automatically tracks your work time and provides insights.. Once connected, OpenClaw can read and act on Rize from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Rize 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 Rize setup: install one ClawHub skill, connect Rize in the browser, and OpenClaw can call real Rize 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 Rize.
1Install 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
Connect Rize
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Rize?"
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-pluginThen 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 Rize in the ClawLink dashboard — paste your Rize API key once.
Verify the connection by asking OpenClaw:
Pull the relevant data from Rize, 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 loginlogin opens the same browser approval and stores a credential locally. Once Rize is connected in the dashboard, that agent calls the same 8 Rize tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Rize MCP for OpenClaw
Looking for a Rize MCP server for OpenClaw? ClawLink connects Rize to OpenClaw and exposes 8 Rize tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Rize integration works the same way.
What the OpenClaw Rize integration can do
8 Rize tools are ready for OpenClaw once the account is connected.
All 8 Rize tools for OpenClaw
| Tool | What it does |
|---|---|
Get cardholder rize_get_cardholder | Retrieve detailed information about a specific cardholder using their unique identifier |
Get virtual card image rize_get_virtual_card_image | Retrieves the virtual card image asset |
Create API key rize_create_api_key | Create a new API key for the partner |
Create card rize_create_card | Creates a new card in the Rize system |
Create cardholder rize_create_cardholder | Creates a new cardholder in the Rize system |
Create counterparty rize_create_counterparty | Creates a new Counterparty in the Rize system |
Create partner financial account rize_create_partner_financial_account | Create a new financial account for an existing partner in the Rize admin API |
Create user rize_create_user | Creates a new user in the Rize system |
Try it: find the Rize tool you need
Browse the 8 Rize 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 Rize, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Rize, summarize it in plain English, and point out anything that needs attention.
Create it in Rize for me, then confirm the important fields before you finish.
Create it in Rize for me, then confirm the important fields before you finish.
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 Rize working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Rize API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Rize 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 Rize. | 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 Rize actions to the runtime in a format your agent can reliably use. | 8 tools for Rize are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Rize 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 Rize in the browser, and the 8 tools above work from chat. There is no SDK and no config file, and the Rize 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 Rize skill but can't call the tools
The ClawHub skill teaches OpenClaw about Rize, but the calls run through the ClawLink plugin and your connected account. Make sure Rize 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 Rize 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 Rize tools
Rize 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 Rize 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.
Rize 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 Rize 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 Rize integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Rize: link your Rize account once in the browser and OpenClaw can call the Rize API through 8 ready-made tools — no custom code or token handling.
How do I add Rize to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Rize skill from ClawHub, then you click Connect in the dashboard to authorize Rize. OpenClaw calls the tools from the next message — no config files, and the Rize key you paste is stored server-side instead of in your environment.
How long does it take to connect Rize to OpenClaw?
About two minutes. Sign in, click Connect next to Rize in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Rize 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 Rize working from chat.
OpenClaw installed the Rize skill but can't call the tools
The ClawHub skill teaches OpenClaw about Rize, but the calls run through the ClawLink plugin and your connected account. Make sure Rize 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.
