Openclaw Skills lets you run APIVoid reputation and verification checks for domains, IPs, URLs, and emails through the oo CLI without handling tokens directly.
Install & Download
1. ClawHub CLI
The fastest way to install a skill directly from the registry.
npx clawhub@latest install oo-api-void
2. Manual Installation
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
3. Prompt Installation
Copy this prompt to OpenClaw to install it automatically.
Help me install oo-api-void using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Prefer to download?
Get the raw skill files in a ZIP archive.
What is APIVoid?
APIVoid is a connector-first skill for running APIVoid from an OOMOL-connected account using the oo CLI. Openclaw Skills uses live schema introspection before every action, so you always build payloads against the authoritative input contract instead of guessing fields.
This skill is designed for secure, repeatable reputation lookups and lightweight account queries. It keeps credentials server-side, returns structured JSON, and makes APIVoid easy to automate for security reviews, email validation, and threat-intelligence workflows.
APIVoid Use Cases
- You need to check a domain's reputation, blacklist status, category flags, or risk score.
- You need to evaluate an IP address before allowlisting, blocking, or investigating it.
- You need to inspect a URL for DNS, blacklist, file, and risk signals.
- You need to verify whether an email address or email domain looks valid before outreach.
- You need to review APIVoid credit, overage, or usage information.
- You want a token-safe, CLI-driven APIVoid workflow for Openclaw Skills and automated agents.
How APIVoid Works
- Choose the APIVoid action that matches the task, such as
check_domain_reputationorverify_email. - Inspect the live contract to learn the exact fields and output shape:
oo connector schema "api_void" --action "<action_name>"
- Build a JSON payload that matches the schema. You can pass it inline or from a file with
--data '<json>'or--data @path/to/file.json. - Execute the action through the OOMOL-connected connector:
oo connector run "api_void" --action "<action_name>" --data '<json>' --json
- Read the structured result from
dataand capturemeta.executionIdfor logging, tracing, or support. - If you hit an auth, scope, or billing error, perform the one-time setup or reconnect step instead of retrying blindly.
APIVoid Setup
Openclaw Skills assumes the oo CLI is installed, you're signed in, and APIVoid is connected in OOMOL. Only do the setup steps below if a command fails with the matching reason.
- Install oo CLI if missing:
curl -fsSL https://cli.oomol.com/install.sh | bash
- Windows PowerShell install:
irm https://cli.oomol.com/install.ps1 | iex
- Sign in once:
oo auth login
- Connect APIVoid in the OOMOL console:
https://console.oomol.com/app-connections?provider=api_void
If you see
scope_missing,credential_expired,app_not_ready, orapp_not_found, reconnect APIVoid from the same console link.If you see HTTP 402 or
OOMOL_INSUFFICIENT_CREDIT, recharge billing before retrying:
https://console.oomol.com/billing/token-recharge
APIVoid Data Schema & Taxonomy
Openclaw Skills uses a simple connector schema model:
| Layer | Shape | Purpose |
|---|---|---|
| Action catalog | check_domain_reputation, check_ip_reputation, check_url_reputation, get_account_info, verify_email |
Defines the available APIVoid operations |
| Input contract | JSON object validated by oo connector schema |
Prevents stale or guessed payload fields |
| Request transport | Inline JSON string or @path/to/file.json |
Lets you automate from shell scripts or saved payloads |
| Response envelope | { "data": ..., "meta": { "executionId": "..." } } |
Returns the result plus an audit-friendly execution id |
| Result data | Reputation, blacklist, risk, DNS, file, account usage fields | Contains the APIVoid payload-specific output |
Files are not generated automatically by the skill. Any JSON files are user-supplied payloads, and the authoritative metadata for each run lives in meta.executionId.
Metadata taxonomy
- Security telemetry: reputation, blacklist status, category flags, risk score
- Network and web signals: DNS, IP, URL, and file-related indicators
- Identity validation: email address and email domain verification
- Account telemetry: credit, overage, and usage information
Always treat the live schema as the source of truth for field names and required inputs.
APIVoid Advanced Features
- Live schema inspection keeps every payload aligned with the current APIVoid contract.
- Server-side credential injection means no raw API keys in prompts, scripts, or local config.
--datasupports inline JSON or@file.json, making Openclaw Skills easy to script.--jsonoutput is machine-friendly for piping into other tools or agents.meta.executionIdenables traceability across retries, logs, and support workflows.- Built-in safety guidance keeps read actions easy to run while preserving confirmation steps for future write or destructive actions.
SKILL.md
Loading
Related Openclaw Skills
Project Daily Recap
A cron-driven Openclaw Skills automation that sends customizable nightly project recap reminders to WeChat without any LLM dependency.
Meta
Openclaw Skills turns Meta into a safe, CLI-driven connector for reading account, campaign, and insights data through an authenticated OOMOL connection.
Lokalise
Openclaw Skills for Lokalise lets you inspect live schemas and safely manage keys, projects, and translations through the oo CLI.
Braze
Braze gives Openclaw Skills users a safe, schema-driven way to read campaigns and canvases through a connected OOMOL account.
Kontent.ai Connector Skill
Openclaw Skills for Kontent.ai lets you inspect content, types, and languages through a schema-driven CLI connector without handling raw credentials.
Discourse Connector
Openclaw Skills for Discourse lets you safely read, search, create, and reply to forum content through the oo CLI.
Featured*
