# How to connect Paradym to OpenClaw (paste one key, 69 tools) > Connect Paradym to OpenClaw with ClawLink: paste your Paradym key once and 69 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/paradym The usual route to Paradym 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 Paradym setup: install one ClawHub skill, connect Paradym in the browser, and OpenClaw can call real Paradym 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 Paradym. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Paradym** — 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 paradym # connect Paradym (browser OAuth) npx -y @useclawlink/cli actions paradym # list available actions npx -y @useclawlink/cli run paradym --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 Paradym in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Paradym API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Paradym, 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: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once Paradym is connected in the dashboard, that agent calls the same 69 Paradym 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). ## Paradym MCP for OpenClaw Looking for a Paradym MCP server for OpenClaw? ClawLink connects Paradym to OpenClaw and exposes 69 Paradym 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 Paradym integration](https://claw-link.dev/hermes/paradym) works the same way. ## What the OpenClaw Paradym integration can do 69 Paradym tools are ready for OpenClaw once the account is connected. The 30 below are the ones people reach for most; your agent can call all 69. ### 30 of 69 Paradym tools for OpenClaw | Tool | What it does | |---|---| | **Get anoncreds credential template** `paradym_get_anoncreds_credential_template` | Retrieve a specific AnonCreds credential template by ID | | **Get anoncreds credential template json schema** `paradym_get_anoncreds_credential_template_json_schema` | Retrieve the JSON schema for an AnonCreds credential template | | **Get di ds** `paradym_get_di_ds` | Retrieve a list of Decentralized Identifiers (DIDs) for a specific project | | **Get did comm connection** `paradym_get_did_comm_connection` | Retrieve a specific DIDComm connection by ID | | **Get did comm connections** `paradym_get_did_comm_connections` | Retrieve a list of DIDComm connections for a project | | **Get didcomm invitation** `paradym_get_didcomm_invitation` | Retrieve a specific DIDComm invitation by ID | | **Get didcomm issuance session** `paradym_get_didcomm_issuance_session` | Retrieve a specific DIDComm issuance session by ID | | **Get mdoc credential template** `paradym_get_mdoc_credential_template` | Retrieve a specific mDoc credential template by ID | | **Get mdoc credential template json schema** `paradym_get_mdoc_credential_template_json_schema` | Retrieve the JSON schema for an mDoc credential template | | **Get openid4vc issuance session** `paradym_get_openid4vc_issuance_session` | Retrieve a specific OpenID4VC issuance session by ID | | **Get openid4vc verification session** `paradym_get_openid4vc_verification_session` | Retrieve a specific OpenID4VC verification session by ID | | **Get presentation template** `paradym_get_presentation_template` | Retrieve a specific presentation template by ID | | **Get presentation templates** `paradym_get_presentation_templates` | Retrieve a list of presentation templates for a project | | **Get project members** `paradym_get_project_members` | Retrieve a list of project members | | **Get project profile** `paradym_get_project_profile` | Retrieve the default profile for a project | | **Get project webhooks** `paradym_get_project_webhooks` | Retrieve a list of webhooks configured for a specific project | | **Get projects** `paradym_get_projects` | Retrieve a list of all projects accessible to the authenticated user | | **Get sd jwt vc credential template** `paradym_get_sd_jwt_vc_credential_template` | Retrieve a specific SD-JWT VC credential template by ID | | **Get sd jwt vc credential template json schema** `paradym_get_sd_jwt_vc_credential_template_json_schema` | Retrieve the JSON schema for an SD-JWT VC credential template | | **Get trusted entities** `paradym_get_trusted_entities` | Retrieve trusted entities for a specific project | | **Get trusted entity** `paradym_get_trusted_entity` | Retrieve a specific trusted entity by ID | | **List anon creds credential templates** `paradym_list_anon_creds_credential_templates` | Retrieve all AnonCreds credential templates for a project | | **List certificate signing requests** `paradym_list_certificate_signing_requests` | Retrieve all certificate signing requests for a project | | **List certificates** `paradym_list_certificates` | Retrieve all X.509 certificates for a project | | **List didcomm invitations** `paradym_list_didcomm_invitations` | Retrieve all DIDComm invitations for a project | | **List didcomm issuance offers** `paradym_list_didcomm_issuance_offers` | List all DIDComm issuance offers within a project | | **List didcomm mediator connections** `paradym_list_didcomm_mediator_connections` | Retrieve connections for a DIDComm mediator | | **List didcomm mediators** `paradym_list_didcomm_mediators` | Retrieve all DIDComm mediators for a project | | **List didcomm verification requests** `paradym_list_didcomm_verification_requests` | List all DIDComm verification sessions for a project | | **List issued credentials** `paradym_list_issued_credentials` | List metadata for all issued credentials within a project | ## Example prompts **Get Anoncreds Credential Template** > Pull the relevant data from Paradym, summarize it in plain English, and point out anything that needs attention. **Get Anoncreds Credential Template Json Schema** > Pull the relevant data from Paradym, summarize it in plain English, and point out anything that needs attention. **Get Di Ds** > Pull the relevant data from Paradym, summarize it in plain English, and point out anything that needs attention. **Get Did Comm Connection** > Pull the relevant data from Paradym, 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 Paradym working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Paradym API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Paradym 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 Paradym. | 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 Paradym actions to the runtime in a format your agent can reliably use. | 69 tools for Paradym are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Paradym 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 Paradym in the browser, and the 69 tools above work from chat. There is no SDK and no config file, and the Paradym 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 Paradym skill but can't call the tools The ClawHub skill teaches OpenClaw about Paradym, but the calls run through the ClawLink plugin and your connected account. Make sure Paradym 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 Paradym 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 Paradym tools Paradym 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 Paradym 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. ### Paradym 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 Paradym has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Paradym integration? Yes. ClawLink is the fastest way to connect OpenClaw to Paradym: link your Paradym account once in the browser and OpenClaw can call the Paradym API through 69 ready-made tools — no custom code or token handling. ### How do I add Paradym to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Paradym skill from ClawHub, then you click Connect in the dashboard to authorize Paradym. OpenClaw calls the tools from the next message — no config files, and the Paradym key you paste is stored server-side instead of in your environment. ### How long does it take to connect Paradym to OpenClaw? About two minutes. Sign in, click Connect next to Paradym in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Paradym 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 Paradym working from chat. ### OpenClaw installed the Paradym skill but can't call the tools The ClawHub skill teaches OpenClaw about Paradym, but the calls run through the ClawLink plugin and your connected account. Make sure Paradym 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 - [OpenClaw GitHub integration](https://claw-link.dev/openclaw/github) — Manage repositories, issues, pull requests, and workflows - [Connect PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture tools](https://claw-link.dev/openclaw/safetyculture) — SafetyCulture (formerly iAuditor) is a workplace operations platform that enables teams to conduct digital inspections, manage audits, track issues, schedule tasks, and maintain compliance through mobile and web applications.