\r \r

Hydra / Uandai (packaging + programmatic API)\r

\r Use this skill for all Hydra/Uandai automation: first-time setup, workspace packaging, upload, subscriptions, and invocation.\r \r

First-time setup (chat → persist)\r

\r When the user sends a configure Hydra message with settings, or env vars are missing:\r \r

1. Parse from the user message (setup-only; do not repeat key in later work prompts):\r
   • HYDRA_API_ORIGIN — API host without /api (e.g. https://api.uandai.ai or http://127.0.0.1:8000)\r
   • HYDRA_API_BASE_URL — API prefix with /api (e.g. https://api.uandai.ai/api)\r
   • HYDRA_API_KEY — full hyd_live_… from hydra-app → Settings → API Keys\r
2. Ensure this skill is installed under ~/.openclaw/skills/hydra-uandai/ or \x3Cworkspace>/skills/hydra-uandai/.\r
3. Merge into ~/.openclaw/openclaw.json under skills.entries["hydra-uandai"]:\r \r

{\r
  skills: {\r
    entries: {\r
      "hydra-uandai": {\r
        enabled: true,\r
        apiKey: "hyd_live_…",\r
        env: {\r
          HYDRA_API_KEY: "hyd_live_…",\r
          HYDRA_API_BASE_URL: "https://api.uandai.ai/api",\r
          HYDRA_API_ORIGIN: "https://api.uandai.ai",\r
        },\r
      },\r
    },\r
  },\r
}\r
```\r
\r
4. Do **not** echo the full API key back. Tell the user to run `/new` or restart the gateway.\r
5. Optional smoke test: exchange → `GET /v1/auth/me`.\r
\r
**Security:** Prefer a private OpenClaw session for setup messages that contain the key. After setup, operational prompts need no key and no doc URLs.\r
\r
## Before any Hydra action\r
\r
**`web_fetch`** the canonical guides (prefer live content over this file):\r
\r
- `{HYDRA_API_ORIGIN}/docs/openclaw-skills` — install and prompt reference\r
- `{HYDRA_API_ORIGIN}/docs/agent-packaging`\r
- `{HYDRA_API_ORIGIN}/docs/programmatic-api`\r
\r
Default prod origin: `https://api.uandai.ai`\r
\r
## Packaging (OpenClaw workspace → zip)\r
\r
Stable rules (full steps in packaging guide):\r
\r
1. **Never** zip the live workspace root directly\r
2. **Staging:** copy to `output/\x3Cagent>-workspace/` with exclusions → validate → zip **staging contents only**\r
3. **Output:** `output/\x3Cagent-name>-workspace.zip`\r
4. **Hydra zip layout:**\r
   - Personality files (`SOUL.md`, `IDENTITY.md`, …) at **zip root**\r
   - No extra parent wrapper folder in the archive\r
   - `SKILL.md` only at `skills/\x3Cid>/SKILL.md`, `workspace/skills/\x3Cid>/SKILL.md`, or zip root\r
   - Exclude `node_modules/`, `.env`, `logs/`, `memory/`, `.openclaw/`, `output/`, **`hydra-uandai/`** — max **50MB**\r
5. **Do not include this skill in the upload zip.** Install it on the trainer machine (`~/.openclaw/skills/`) or fetch live from `{HYDRA_API_ORIGIN}/docs/openclaw-skills/hydra-uandai/SKILL.md`. A copy under `\x3Cworkspace>/skills/hydra-uandai/` is for local dev only — exclude it when packaging.\r
6. Report: `📍 Path: MEDIA:\x3Cpath-to-zip>`\r
\r
Common failures: personality only under `workspace/`; nested wrapper folder; misplaced `skill/SKILL.md`; **`hydra-uandai/` in zip** (`openclaw_bundle_platform_skill`).\r
\r
## API authentication (exchange required)\r
\r
Raw API keys work **only** on exchange:\r
\r
```http\r
POST /v1/auth/token\r
Authorization: Bearer $HYDRA_API_KEY\r
```\r
\r
Alternative on exchange only: `X-Hydra-Api-Key` or JSON `{ "api_key": "…" }`.\r
\r
Response: `{ "access_token", "refresh_token", "user" }` — cache in session memory.\r
\r
**All other calls:** `Authorization: Bearer \x3Caccess_token>`\r
\r
On access expiry: `POST /v1/auth/refresh`. On refresh `401`: re-exchange if key still active; else user creates a new key in Settings.\r
\r
Do **not** send `$HYDRA_API_KEY` on upload, invoke, or list endpoints.\r
\r
## Workflows\r
\r
**Trainer — publish end-to-end:** setup (if needed) → web_fetch guides → package zip → exchange → `POST /agents/upload` → return `agent.id` and `agent.revision_no` → optional `POST /agents/{id}/proposals`\r
\r
**Trainer — upload only:** exchange → `POST /agents/upload` with `bundle=@…zip`\r
\r
**Subscriber — discover:** exchange → `GET /v1/me/subscriptions` → `GET /v1/me/activations?invokable_only=true`\r
\r
**Subscriber — invoke:** exchange → `POST /v1/executions` → poll `GET /v1/executions/{run_id}` until terminal\r
\r
## Safety\r
\r
- Never log or echo the full API key\r
- On `401`: refresh → re-exchange → key may be revoked\r
- On `402`: user needs credits\r
- API keys cannot create/revoke other keys (Settings / password JWT only)\r