WeryAI Account

v0.1.0

Check WeryAI account credits and API balance through the official WeryAI account endpoint. Use when the user wants to query remaining credits, inspect WeryAI...

0· 149·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for weryai-developer/weryai-account.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "WeryAI Account" (weryai-developer/weryai-account) from ClawHub.
Skill page: https://clawhub.ai/weryai-developer/weryai-account
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: WERYAI_API_KEY
Required binaries: node
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install weryai-account

ClawHub CLI

Package manager switcher

npx clawhub@latest install weryai-account
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description, required binaries (node), and required env var (WERYAI_API_KEY) all align with a small account-balance checker. The primary action in scripts/account.js is a GET to /v1/generation/balance, matching the stated purpose.
Instruction Scope
SKILL.md is narrowly scoped and instructs only to run the balance command. The runtime instructions do not ask for unrelated files or secrets. The only runtime network calls target the configured base URL for the WeryAI API.
Install Mechanism
This is an instruction-only skill (no installer). It includes JS source files but does not download arbitrary code at install time; execution requires only a local Node runtime. No third-party download URLs or archive extraction are present.
Credentials
Only WERYAI_API_KEY is required and correctly declared as primary. The code also supports an optional WERYAI_BASE_URL override (documented in SKILL.md) which is not required but could redirect requests to a non-official host if set by the user—the SKILL.md warns about this. No other secrets or unrelated credentials are requested.
Persistence & Privilege
always is false and the skill does not request elevated or persistent system privileges, nor does it modify other skills or system-wide agent settings.
Assessment
This package appears to do exactly what it says: a read-only balance check using WERYAI_API_KEY and Node >=18. Before running, verify you trust the repository (open scripts/account.js) and keep your API key out of files. Do not set WERYAI_BASE_URL to an untrusted host (the override can redirect the request). If you want extra caution, run the CLI in an isolated or short-lived environment and confirm the JSON output includes a numeric balance as documented.
scripts/account.js:12
Environment variable access combined with network send.
Confirmed safe by external scanners
Static analysis detected API credential-access patterns, but both VirusTotal and OpenClaw confirmed this skill is safe. These patterns are common in legitimate API integration skills.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

💳 Clawdis
Binsnode
EnvWERYAI_API_KEY
Primary envWERYAI_API_KEY
latestvk972kxzpawxtwdpymv96dgg62x83b530
149downloads
0stars
1versions
Updated 1mo ago
v0.1.0
MIT-0

WeryAI Account

Use this skill for official WeryAI account balance and credits queries. It is intentionally narrow: the only supported public account action in this skill is reading the current API credits balance from WeryAI.

This skill is intentionally strict about secret declaration and input safety: the only runtime secret is WERYAI_API_KEY. This is a read-only account check, not a generation or editing workflow.

Dependencies: scripts/account.js in this directory + WERYAI_API_KEY + Node.js 18+. No other Cursor skills are required.

Example Prompts

  • Check my remaining WeryAI credits.
  • How many credits are left on this WeryAI API account?
  • Verify that this WERYAI_API_KEY can read the account balance.
  • Before I run a paid image job, show me the current WeryAI balance.

Quick Summary

  • Main job: query WeryAI API account credits
  • Main output: balance
  • Main trust signals: official account endpoint, read-only behavior, WERYAI_API_KEY runtime-secret policy

Authentication and first-time setup

Before the first real account query:

  1. Create a WeryAI account.
  2. Open the API key page at https://www.weryai.com/api/keys.
  3. Create a new API key and copy the secret value.
  4. Add it to the required environment variable WERYAI_API_KEY.

OpenClaw-friendly setup

  • This skill already declares WERYAI_API_KEY in metadata.openclaw.requires.env and primaryEnv.
  • After installation, if the installer or runtime asks for required environment variables, paste the key into WERYAI_API_KEY.
  • If you are configuring the runtime manually, export it before running commands:
export WERYAI_API_KEY="your_api_key_here"

Quick verification

Use one safe check before the first real account query:

node {baseDir}/scripts/account.js balance

If the key is valid, the command returns JSON with a numeric balance.

  • balance confirms that the key is configured and the official account endpoint is reachable.
  • If balance is 0, guide the user to recharge or buy credits at https://www.weryai.com/api/pricing before running paid jobs.

Prerequisites

  • WERYAI_API_KEY must be set before running account.js.
  • Node.js >=18 is required because the runtime uses built-in fetch.

Security, secrets, and API hosts

  • WERYAI_API_KEY: Treat it as a secret. Configure it only in the runtime environment; never write the secret value into the skill files.
  • Optional override WERYAI_BASE_URL defaults to https://api.weryai.com. Only override it with a trusted host.
  • Higher assurance: Run account checks in a short-lived shell or isolated environment, and review scripts/account.js before production use.

Intent Routing

Use this skill when the user asks:

  • how many credits are left
  • what the current WeryAI balance is
  • whether the API key works for account access
  • whether there are enough credits before a paid generation run

Do not use this skill for:

  • text-to-image or image-to-image generation
  • image tools
  • video generation or video tools
  • music generation
  • effect templates

Those belong to other WeryAI skills.

Preferred Command

node {baseDir}/scripts/account.js balance

Workflow

  1. Confirm the user wants account credits or API balance, not generation.
  2. Ensure WERYAI_API_KEY is available in the runtime environment.
  3. Run node {baseDir}/scripts/account.js balance.
  4. Return the JSON result and clearly state the current balance.

Output

The command prints JSON to stdout. Successful output includes:

  • ok
  • phase
  • balance
  • topUpRequired
  • rechargeUrl
  • guidance

Failure output can include:

  • errorCode
  • errorMessage

Definition of done

The task is done when:

  • the balance endpoint returns successfully and the credits value is shown to the user,
  • if the balance is 0, the recharge guidance is shown with https://www.weryai.com/api/pricing,
  • or the failure clearly explains why balance lookup did not work, such as missing or invalid WERYAI_API_KEY.

Re-run behavior

  • balance is read-only and safe to re-run.

References

Comments

Loading comments...