Parallect.ai
Integrations

OpenClaw

Use Parallect with OpenClaw by downloading SKILL.md from Integrations and following setup for your OpenClaw environment.

OpenClaw

OpenClaw is an environment where skills -- packaged instructions and metadata -- teach assistants how to use external services. Parallect ships a SKILL.md you can download so OpenClaw-aware setups know how to call Parallect consistently.

What OpenClaw is

In this context, think of OpenClaw as a skill host: you add a skill (Markdown + conventions), and tools that understand that format can follow the skill to authenticate, hit endpoints, or sequence actions. Parallect's skill focuses on getting you productive without re-deriving URLs and auth patterns from scratch.

OpenClaw evolves independently -- if something doesn't match your build, compare with the latest OpenClaw docs and the SKILL.md comments.

Downloading SKILL.md

  1. Open Integrations in Parallect.
  2. Locate the OpenClaw card.
  3. Use Download SKILL.md (or the equivalent action in the setup dialog).

Save the file somewhere your OpenClaw installation expects skills to live -- often a skills directory or a path configured in your OpenClaw config.

Setup instructions

After download:

  1. Place SKILL.md in the folder OpenClaw scans for skills (follow OpenClaw's README for the exact path).
  2. Configure secrets -- You'll still need a Parallect API key for authenticated calls. Create one under API keys and inject it the way OpenClaw recommends (env var, secret store, or local override -- never commit keys).
  3. Reload or restart the OpenClaw process so it picks up the new skill.
  4. Smoke-test with a small action -- e.g. a read-only request or whatever the SKILL prescribes as a hello-world.

The SKILL file is the source of truth for command names, parameters, and safety notes specific to Parallect's integration.

MCP and REST context

OpenClaw may use REST calls, MCP, or both depending on your stack. Parallect's MCP URL is:

https://parallect.ai/api/mcp/mcp

If the SKILL points you at HTTP APIs instead, use the same API key you use for other integrations.


Back to Integrations overview or continue with API keys.

On this page