# Oo Keyzy

> KEYZY (keyzy.io). Use this skill for ANY KEYZY request — reading, creating, updating, and deleting data. Whenever a task involves KEYZY, use this skill instead of calling the API directly.

- Skill: `oomol-lab/oo-keyzy` (Agent Skill)
- Install (CLI): `npx get-skill add oomol-lab/oo-keyzy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oomol-lab/oo-keyzy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: oomol-lab (https://skillmd.com/u/oomol-lab)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/oomol-lab/oo-keyzy

---


# KEYZY

Operate **KEYZY** through your OOMOL-connected account. This skill calls the `keyzy` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.

## Running an action

Assume the user has already installed the oo CLI, signed in, and connected KEYZY. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.

**1. Inspect the contract** to get the authoritative input/output schema before building a payload:

```bash
oo connector schema "keyzy" --action "<action_name>"
```

**2. Run the action** with a JSON payload that matches the input schema:

```bash
oo connector run "keyzy" --action "<action_name>" --data '<json>' --json
```

- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.

Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.

## Available actions

- `delete_license` — Delete a license and all its activations. The supplied type must match the license type. [destructive]
- `get_license` — Get license details by serial number.
- `register_license` — Register a customer to a license. SKU settings control whether KEYZY emails the license. [write]
- `update_license_sku` — Change the SKU associated with a license. [write]
- `update_license_time` — Update the end time and optional start time of a subscription or trial license. [write]

## Safety

- Untagged actions are reads (get / list / search) — safe to run directly.
- **Actions tagged `[write]` change KEYZY state — confirm the exact payload and effect with the user before running.**
- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**

## First-time setup

These are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

- **`oo: command not found`** — install the oo CLI (other platforms: <https://cli.oomol.com/install-guide.md>):

  ```bash
  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  ```

  ```powershell
  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  ```

- **Not signed in / authentication error** — sign in to your OOMOL account once:

  ```bash
  oo auth login
  ```

- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — KEYZY is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  ```text
  https://console.oomol.com/connections/keyzy
  ```

- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources

- KEYZY homepage: https://www.keyzy.io/
- API documentation: https://www.keyzy.io/docs/developers/rest-api/general-requirements/

