# How to connect Bigml to Hermes Agent (paste one key, 45 tools)

> Connect Bigml to Hermes with ClawLink: paste your Bigml key once and 45 tools work from chat. No MCP server to run, nothing stored on your machine.

Web version: https://claw-link.dev/hermes/bigml

Most guides for giving Hermes Agent Bigml 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 Bigml setup: pair once in the browser and your always-on Hermes agent can act on Bigml 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 Bigml.

1. **Install ClawLink** — add the plugin to Hermes Agent once.
2. **Connect Bigml** — 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 bigml  # connect Bigml (browser OAuth)
npx -y @useclawlink/cli actions bigml  # list available actions
npx -y @useclawlink/cli run bigml <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 Bigml in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your Bigml API key once.

Verify the connection by asking Hermes:

> Pull the relevant data from Bigml, 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 Bigml is connected in the dashboard, that agent calls the same 45 Bigml 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).

## Bigml MCP for Hermes

Looking for a Bigml MCP server for Hermes Agent? ClawLink connects Bigml to Hermes Agent and exposes 45 Bigml 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 Bigml integration](https://claw-link.dev/openclaw/bigml) works the same way.

## What the Hermes Agent Bigml integration can do

45 Bigml 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 45.

### 30 of 45 Bigml tools for Hermes

| Tool | What it does |
|---|---|
| **Get configuration** `bigml_get_configuration` | Retrieves complete details of a BigML configuration by its ID to get stored parameters |
| **Get external connector** `bigml_get_external_connector` | Retrieves complete details of a BigML external connector by its ID |
| **Get project** `bigml_get_project` | Retrieve details of a project by ID |
| **Get source** `bigml_get_source` | Retrieves complete details of a BigML source by its ID |
| **List anomalies** `bigml_list_anomalies` | List anomaly detector resources in your account |
| **List anomaly scores** `bigml_list_anomaly_scores` | List anomaly score resources |
| **List association sets** `bigml_list_association_sets` | List association set resources in your account |
| **List associations** `bigml_list_associations` | List association resources |
| **List batch anomaly scores** `bigml_list_batch_anomaly_scores` | List batch anomaly score resources |
| **List batch centroids** `bigml_list_batch_centroids` | List all batch centroid resources in your account with support for filtering, ordering, and |
| **List batch predictions** `bigml_list_batch_predictions` | List batch prediction resources |
| **List batch projections** `bigml_list_batch_projections` | List batch projection resources with support for filtering, ordering, and pagination |
| **List batch topic distributions** `bigml_list_batch_topic_distributions` | List batch topic distribution resources |
| **List centroids** `bigml_list_centroids` | List centroid resources |
| **List clusters** `bigml_list_clusters` | List cluster resources with support for filtering, ordering, and pagination |
| **List composites** `bigml_list_composites` | List composite source resources |
| **List configurations** `bigml_list_configurations` | List all configuration resources in your account |
| **List correlations** `bigml_list_correlations` | List correlation resources |
| **List datasets** `bigml_list_datasets` | List dataset resources |
| **List deepnets** `bigml_list_deepnets` | List deep neural network resources |
| **List ensembles** `bigml_list_ensembles` | List ensemble resources with filtering, ordering, and pagination support |
| **List evaluations** `bigml_list_evaluations` | List evaluation resources |
| **List executions** `bigml_list_executions` | List execution resources |
| **List forecasts** `bigml_list_forecasts` | List forecast resources |
| **List fusions** `bigml_list_fusions` | List fusion resources |
| **List libraries** `bigml_list_libraries` | List WhizzML library resources |
| **List linear regressions** `bigml_list_linear_regressions` | List linear regression resources |
| **List logistic regressions** `bigml_list_logistic_regressions` | List logistic regression resources |
| **List models** `bigml_list_models` | List model resources |
| **List optimls** `bigml_list_optimls` | List OptiML resources in your account |

## Example prompts

**Get Configuration**

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

**Get External Connector**

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

**Get Project**

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

**Get Source**

> Pull the relevant data from Bigml, 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 Bigml working from chat.

| | Manual | ClawLink |
|---|---|---|
| **Credential handling** | Collect, validate, store, and rotate the Bigml API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Bigml 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 Bigml. | 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 Bigml actions to the runtime in a format your agent can reliably use. | 45 tools for Bigml are already exposed through ClawLink, so the agent can read and act from chat immediately. |

## ClawLink vs. Composio

Composio also exposes Bigml 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 Bigml in the browser, and the 45 tools above work from chat. There is no SDK and no config file, and the Bigml 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 Bigml
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 Bigml 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 Bigml tools
Bigml 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 Bigml 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.

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

### How do I connect Bigml 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 Bigml in the dashboard and Hermes can use it from the next message — no config files, and the Bigml key you paste is stored server-side instead of in your environment.

### How long does it take to connect Bigml to Hermes Agent?
About two minutes. Sign in, click Connect next to Bigml in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

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

### Hermes paired but still can't use Bigml
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

- [Connect DataRobot](https://claw-link.dev/hermes/datarobot) — DataRobot is a machine learning platform that automates model building, deployment, and monitoring, enabling organizations to derive predictive insights from large datasets.
- [Connect Chatbotkit](https://claw-link.dev/hermes/chatbotkit) — ChatBotKit is a platform that enables developers to build and manage AI-powered chatbots, offering comprehensive APIs and SDKs for seamless integration into applications.
- [Hermes Just One API integration](https://claw-link.dev/hermes/just-one-api) — Just One API provides unified access to public social media, creator, entertainment, and ecommerce data across hundreds of metered endpoints.
