# How to connect Accredible certificates to Hermes Agent (paste one key, 36 tools)

> Connect Accredible certificates to Hermes 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/hermes/accredible-certificates

Most guides for giving Hermes Agent Accredible certificates access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Accredible certificates setup: pair once in the browser and your always-on Hermes agent can act on Accredible certificates for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

## Setup

It takes three steps to connect Hermes to Accredible certificates.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Accredible certificates** — one-click OAuth in the ClawLink dashboard.
3. **Use it from chat** — ask Hermes Agent in plain English.

**Paste this into Hermes to set up ClawLink:**

> Set up ClawLink for Hermes and tell me when it's ready.
> 1. Install the plugin: `hermes plugins install ClawLink-HQ/hermes-plugin --enable`
> 2. Start pairing with `hermes clawlink begin`. It prints an approval link, so show me the link and stop, don't wait.
> 3. I'll approve it in my browser, then reply "approved".
> 4. When I say approved, finish setup: `hermes clawlink finish`
> 5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.

**Alternative for any agent (no plugin needed):** if the Hermes Agent 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 <action> --input '<json>'  # execute (add --confirm for writes)
```

### Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

```bash
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test
```

Then connect Accredible certificates in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Accredible certificates API key once.

Verify the connection by asking Hermes:

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

### Using a different agent?

The Hermes 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 Hermes

Looking for a Accredible certificates MCP server for Hermes Agent? ClawLink connects Accredible certificates to Hermes Agent 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 OpenClaw instead? The [OpenClaw Accredible certificates integration](https://claw-link.dev/openclaw/accredible-certificates) works the same way.

## What the Hermes Agent Accredible certificates integration can do

36 Accredible certificates tools are ready for Hermes Agent 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 Hermes

| 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 Hermes Agent. 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 Hermes Agent 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.

### Hermes paired but still can't use Accredible certificates
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

### 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 Hermes Agent Accredible certificates integration?
Yes. ClawLink is the fastest way to connect Hermes to Accredible certificates: link your Accredible certificates account once in the browser and Hermes Agent can call the Accredible certificates API through 36 ready-made tools — no custom code or token handling.

### How do I connect Accredible certificates to Hermes with ClawLink?
Install the plugin with `hermes plugins install ClawLink-HQ/hermes-plugin --enable`, then pair once: run `hermes clawlink begin`, approve the link in your browser, and run `hermes clawlink finish`. Connect Accredible certificates in the dashboard and Hermes can use it 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 Hermes Agent?
About two minutes. Sign in, click Connect next to Accredible certificates in the dashboard, authenticate, and Hermes Agent 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 Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Accredible certificates working from chat.

### Hermes paired but still can't use Accredible certificates
Pairing is a two-step handshake: run `hermes clawlink begin`, approve the link in your browser, then run `hermes clawlink finish`. If you ran finish before approving, or the approval link expired, run `hermes clawlink begin` again to get a fresh link. Confirm the plugin was installed with `--enable`, then verify with `hermes clawlink test`.

## Related

- [GitHub tools](https://claw-link.dev/hermes/github) — Manage repositories, issues, pull requests, and workflows
- [PagerDuty tools](https://claw-link.dev/hermes/pagerduty) — Manage incidents, on-call schedules, and services
- [Connect SafetyCulture](https://claw-link.dev/hermes/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.
