# How to connect Accredible certificates to OpenClaw (paste one key, 36 tools) > Connect Accredible certificates to OpenClaw with ClawLink: paste your Accredible certificates key once and 36 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/accredible-certificates The usual route to Accredible certificates 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 Accredible certificates setup: install one ClawHub skill, connect Accredible certificates in the browser, and OpenClaw can call real Accredible certificates 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 Accredible certificates. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect Accredible certificates** — 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 accredible-certificates # connect Accredible certificates (browser OAuth) npx -y @useclawlink/cli actions accredible-certificates # list available actions npx -y @useclawlink/cli run accredible-certificates --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 Accredible certificates in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Accredible certificates API key once. Verify the connection by asking OpenClaw: > Pull the relevant data from Accredible certificates, 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 Accredible certificates is connected in the dashboard, that agent calls the same 36 Accredible certificates 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). ## Accredible certificates MCP for OpenClaw Looking for a Accredible certificates MCP server for OpenClaw? ClawLink connects Accredible certificates to OpenClaw and exposes 36 Accredible certificates 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 Accredible certificates integration](https://claw-link.dev/hermes/accredible-certificates) works the same way. ## What the OpenClaw Accredible certificates integration can do 36 Accredible certificates 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 36. ### 30 of 36 Accredible certificates tools for OpenClaw | Tool | What it does | |---|---| | **Get analytics** `accredible_certificates_get_analytics` | Retrieve analytics data for credentials | | **Get credential** `accredible_certificates_get_credential` | View a credential by ID | | **Get credential analytics** `accredible_certificates_get_credential_analytics` | View analytics for a specific credential | | **Get department** `accredible_certificates_get_department` | View a specific department by ID | | **Get evidence item** `accredible_certificates_get_evidence_item` | Retrieve a specific evidence item from a credential | | **Get group** `accredible_certificates_get_group` | Retrieve a specific group by ID | | **Get issuer** `accredible_certificates_get_issuer` | Retrieve details about the authenticated issuer | | **Get reference** `accredible_certificates_get_reference` | View a specific reference by ID | | **List templates** `accredible_certificates_list_templates` | Retrieve a list of all templates | | **Search attribute keys** `accredible_certificates_search_attribute_keys` | Search for attribute keys by various criteria | | **Search collections** `accredible_certificates_search_collections` | Search for collections | | **Search credentials v2** `accredible_certificates_search_credentials_v2` | Search for credentials using the v2 API | | **Search departments** `accredible_certificates_search_departments` | Search for departments by various criteria | | **Search designs** `accredible_certificates_search_designs` | Search for designs (certificate/badge templates) | | **Search groups** `accredible_certificates_search_groups` | Search for groups in Accredible | | **View all skill categories** `accredible_certificates_view_all_skill_categories` | Retrieve all skill categories | | **Bulk create credentials v2** `accredible_certificates_bulk_create_credentials_v2` | Bulk create credentials | | **Clone group** `accredible_certificates_clone_group` | Clone an existing group | | **Create attribute key** `accredible_certificates_create_attribute_key` | Create a new custom attribute key | | **Create collection** `accredible_certificates_create_collection` | Create a new collection | | **Create credential** `accredible_certificates_create_credential` | Create a new credential with optional evidence items and references | | **Create evidence item** `accredible_certificates_create_evidence_item` | Create a new evidence item for a credential | | **Create group** `accredible_certificates_create_group` | Create a new group | | **Create reference** `accredible_certificates_create_reference` | Create a new reference for a credential | | **Generate pd fs for credentials** `accredible_certificates_generate_pd_fs_for_credentials` | Generate PDFs for multiple credentials | | **Initialize badge designer** `accredible_certificates_initialize_badge_designer` | Initialize the embedded badge designer | | **Initialize certificate designer** `accredible_certificates_initialize_certificate_designer` | Initialize the embedded certificate designer | | **Update credential** `accredible_certificates_update_credential` | Update an existing credential | | **Update evidence item** `accredible_certificates_update_evidence_item` | Update an existing evidence item for a credential | | **Update group** `accredible_certificates_update_group` | Update an existing group | ## Example prompts **Get Analytics** > Pull the relevant data from Accredible certificates, summarize it in plain English, and point out anything that needs attention. **Get Credential** > Pull the relevant data from Accredible certificates, summarize it in plain English, and point out anything that needs attention. **Get Credential Analytics** > Pull the relevant data from Accredible certificates, summarize it in plain English, and point out anything that needs attention. **Get Department** > Pull the relevant data from Accredible certificates, 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 Accredible certificates working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the Accredible certificates API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Accredible certificates 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 Accredible certificates. | 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 Accredible certificates actions to the runtime in a format your agent can reliably use. | 36 tools for Accredible certificates are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes Accredible certificates 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 Accredible certificates in the browser, and the 36 tools above work from chat. There is no SDK and no config file, and the Accredible certificates 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 Accredible certificates skill but can't call the tools The ClawHub skill teaches OpenClaw about Accredible certificates, but the calls run through the ClawLink plugin and your connected account. Make sure Accredible certificates 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 Accredible certificates 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 Accredible certificates tools Accredible certificates 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 Accredible certificates 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. ### Accredible certificates 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 Accredible certificates has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw Accredible certificates integration? Yes. ClawLink is the fastest way to connect OpenClaw to Accredible certificates: link your Accredible certificates account once in the browser and OpenClaw can call the Accredible certificates API through 36 ready-made tools — no custom code or token handling. ### How do I add Accredible certificates to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Accredible certificates skill from ClawHub, then you click Connect in the dashboard to authorize Accredible certificates. OpenClaw calls the tools from the next message — no config files, and the Accredible certificates key you paste is stored server-side instead of in your environment. ### How long does it take to connect Accredible certificates to OpenClaw? About two minutes. Sign in, click Connect next to Accredible certificates in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring Accredible certificates 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 Accredible certificates working from chat. ### OpenClaw installed the Accredible certificates skill but can't call the tools The ClawHub skill teaches OpenClaw about Accredible certificates, but the calls run through the ClawLink plugin and your connected account. Make sure Accredible certificates 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 - [PagerDuty](https://claw-link.dev/openclaw/pagerduty) — Manage incidents, on-call schedules, and services - [SafetyCulture](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.