Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Pay for APIs, tools, and services from your agent's Kash wallet. Spends below $5 are autonomous; above $5 requires explicit user YES. Requires KASH_KEY and K...
Pay for APIs, tools, and services from your agent's Kash wallet. Spends below $5 are autonomous; above $5 requires explicit user YES. Requires KASH_KEY and K...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill gives your OpenClaw agent access to a Kash wallet so it can pay for external services autonomously, within your configured budget.
KASH_KEY and KASH_AGENT_ID are required. The skill will fail at load time if either is missing โ it will not silently proceed. KASH_API_URL is validated against an allowlist (api.kash.dev and localhost only) at startup. Setting it to any other domain is rejected immediately to prevent KASH_KEY from being sent to an untrusted server. KASH_BUDGET is enforced locally in code as a session cap. It is not just a guideline โ the spend function checks it before every call. Spends above KASH_SPEND_CONFIRMATION_THRESHOLD ($5.00 default) require confirmed=true, which the agent must only set after receiving an explicit YES from the user in the current conversation. Budget enforcement happens at two layers: locally (KASH_BUDGET) and server-side (Kash dashboard budget). Both must pass. The server is the authoritative source of truth.
Spend from the Kash agent wallet before making a paid API call. Parameters: amount (number, required) โ amount in USD description (string, required) โ what you are paying for merchant (string, optional) โ name of the service confirmed (boolean, optional) โ set true only after explicit user YES for spends above threshold Return values: OK. Spent $X for "..." โ spend succeeded CONFIRMATION_REQUIRED: ... โ ask user for YES, then retry with confirmed=true LOCAL_BUDGET_EXCEEDED: ... โ session cap hit, stop and notify user BUDGET_EXCEEDED: ... โ server-side budget hit, stop and notify user AGENT_PAUSED: ... โ agent paused by user in Kash dashboard UNAUTHORIZED: ... โ KASH_KEY invalid or expired ERROR: ... โ unexpected failure
Check remaining budget without spending. Returns both server-side balance and local session cap.
Use kash_spend BEFORE making any paid external call โ API calls, web searches, data purchases, or any service that charges per request. Always call it before the paid operation, not after. Use kash_balance before starting a multi-step task that will require several paid operations.
Always call kash_spend BEFORE the paid call, never after If CONFIRMATION_REQUIRED is returned, ask the user for explicit YES โ never bypass it If BUDGET_EXCEEDED or LOCAL_BUDGET_EXCEEDED is returned, stop the task immediately and tell the user Never set confirmed=true without a real user confirmation in the current conversation Never attempt to work around a budget limit If kash_spend returns any error, do NOT proceed with the paid call
Use this skill to pay for external APIs, tools, and services from your Kash agent wallet.
Configure in ~/.openclaw/openclaw.json: { "skills": { "entries": { "kash": { "enabled": true, "apiKey": "ksh_live_...", "env": { "KASH_KEY": "ksh_live_...", "KASH_AGENT_ID": "your-agent-id", "KASH_BUDGET": "50", "KASH_SPEND_CONFIRMATION_THRESHOLD": "5.00" } } } } } Get KASH_KEY and KASH_AGENT_ID from kash.dev/dashboard/agents after registering your agent.
Call this BEFORE any paid API call or service. Never after. Parameters: amount (number, required) โ cost in USD e.g. 0.003 description (string, required) โ what you are paying for e.g. "serper web search" merchant (string, optional) โ service name e.g. "Serper" confirmed (boolean, optional) โ set true ONLY after explicit user YES for spends above threshold Returns: OK. Spent $X for "..." โ proceed with the paid call CONFIRMATION_REQUIRED: ... โ ask user for YES, then retry with confirmed=true LOCAL_BUDGET_EXCEEDED: ... โ stop, tell user to top up at kash.dev BUDGET_EXCEEDED: ... โ stop, tell user to top up at kash.dev AGENT_PAUSED: ... โ tell user to resume agent at kash.dev/dashboard/agents UNAUTHORIZED: ... โ tell user their KASH_KEY may be invalid ERROR: ... โ do not proceed with the paid call
Check remaining budget. Use before starting multi-step paid tasks. No parameters required.
Always call kash_spend BEFORE the paid call, never after If CONFIRMATION_REQUIRED is returned, ask the user for explicit YES before retrying with confirmed=true If any error or budget exceeded is returned, stop immediately and tell the user Never set confirmed=true without a real user YES in the current conversation Never attempt to work around a budget limit Never reveal KASH_KEY value in any message or log
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.