Legal Disclaimer
PipeAgent is a data distribution gateway. We do not own, verify, or endorse the data provided by third-party creators. Use at your own discretion.
OpenClaw: PipeAgent Pilot
PipeAgent Pilot is a controller OpenClaw skill: the user talks to the agent, which uses read-keyed JSON APIs to search or browse feeds, inspect metadata (consumer_type, schema, pricing hints), then runs install.sh in the shell to add the per-feed SKILL.md.
For copy-paste terminal install without going through chat, use OpenClaw · CLI install. For a comparison of both approaches, see OpenClaw Integration.
One-line install (recommended)
Same pattern as feed install.sh: no Read key in the command; writes ~/.openclaw/workspace/skills/pipeagent-pilot/SKILL.md (workspace must exist, or use --dest).
curl -fsSL https://pipeagent.dev/install-pipeagent-pilot.sh | bashOptional flags:
--dest <openclaw_workspace_root>: set a custom OpenClaw workspace root.--site <web_origin>: only when support gives you a custom download host.--key <read_key>: write PROVIDER_READ_API_KEY after install.--env-file <path>: target env file (default ~/.openclaw/.env).--yes: auto-confirm prompts.Env on bash: PIPEAGENT_WEB_ORIGIN (same meaning as --site).
Beginner-friendly examples
Install and then input key interactively:
curl -fsSL https://pipeagent.dev/install-pipeagent-pilot.sh | bashInstall and set key non-interactively:
curl -fsSL https://pipeagent.dev/install-pipeagent-pilot.sh | bash -s -- --key "pa_xxx"Install with a custom env path:
curl -fsSL https://pipeagent.dev/install-pipeagent-pilot.sh | bash -s -- --env-file "~/.openclaw/.env" --yesRaw SKILL.md URL
No API key: https://pipeagent.dev/pipeagent-pilot/SKILL.md — use if you prefer manual mkdir + curl -o instead of the installer script.
After install:
1. Reload skills so pipeagent-pilot is available.
- Restart OpenClaw Gateway only when PROVIDER_READ_API_KEY was newly added or changed.
2. Ask in chat: Please refresh skills and confirm pipeagent-pilot is available.
Prerequisites
1. Read API key — Create a read key in the Dashboard. The pilot uses it for /v1/catalog, /v1/search, and /v1/feed/{id}/metadata (see Authentication).
2. PROVIDER_READ_API_KEY — Set in the OpenClaw runtime (e.g. agent .env). Same variable the installed feed skills use to call GET /v1/feed/{id}. Newer install.sh can prompt to write this into default OpenClaw env (~/.openclaw/.env) or a custom --env-file. Where OpenClaw loads env: OpenClaw environment variables.
3. OpenClaw workspace — Default ~/.openclaw/workspace must exist before install.sh runs (or pass --dest). See CLI install for details.
What the pilot does (for you and the model)
| Step | Action | |
|---|---|---|
| Discover | GET https://api.pipeagent.dev/v1/catalog?limit=…&offset=… and/or GET …/v1/search?q=… with read key | |
| Inspect | GET …/v1/feed/{uuid_or_endpoint_path}/metadata with read key | |
| Install feed skill | Shell: `curl -fsSL https://pipeagent.dev/install.sh \ | bash -s -- --alias "…"` — no read key in this command |
{id} in metadata is either the feed UUID or endpoint_path (same as ALIAS on the feed page).limit (1–100, default 20), offset, and response fields total / has_more.Full behavioral spec is in the downloaded SKILL.md (instructions block).
Machine-readable API
Agents can use openapi.json for path and parameter details.