Yukkai Cloud Tool

What is it?

The Yukkai Cloud tool gives you read-only access to account-level information tied to your Yukkai setup. It covers two main areas:

• OpenRouter key status — how much you've spent, what your credit limit is, and how much remains.
• Cloud Code (Parse) backend health — a quick check that the Symbyoz Cloud Code server is up and reachable.

It does not expose your raw API key at any point; the key is always masked in responses.

How it works

The tool talks to two backends:

1. Cloud Code (Parse) — Yukkai's own cloud backend. It stores a hash of your OpenRouter key and can look up full account details on your behalf.
2. OpenRouter API — direct calls to OpenRouter using your active key to fetch live usage data.

No sensitive credentials are ever returned in the response. The tool is purely informational — it reads data, it never writes or modifies anything.

How to use it

The tool exposes three actions. All of them are read-only and require no parameters (with one optional exception).

Action	Description	Parameters
openrouter_key_usage	Fetches live usage, credit limits, and remaining balance from OpenRouter using the active key.	None
openrouter_key_info	Retrieves full key details via the Cloud Code backend (requires a keyHash stored in the Vault).	key_hash (optional — defaults to the active account's stored hash)
health	Checks the status of the Cloud Code (Parse) server.	None

Which action should I use?

• Want to know how much credit you have left? → Use openrouter_key_usage. It's the simplest and fastest path.
• Need full account/key metadata from the backend? → Use openrouter_key_info. This goes through Cloud Code and requires a key hash to be stored in the Vault.
• Troubleshooting connectivity? → Use health to confirm the Cloud Code server is online.

Examples

Check your OpenRouter credit balance

Simply ask Yukkai something like:

"How much OpenRouter credit do I have left?"

Yukkai will call openrouter_key_usage and report your current usage, limit, and remaining credits.

Get full key details from the backend

"Give me my full OpenRouter key info from the cloud."

Yukkai will call openrouter_key_info, which routes through the Cloud Code backend. If a key hash is already stored in the Vault, you don't need to supply anything.

Check Cloud Code server health

"Is the Cloud Code backend up?"

Yukkai will call health and tell you whether the Parse server is reachable.

Tips & best practices

• Prefer openrouter_key_usage over openrouter_key_info. It's a direct call to OpenRouter, needs no extra configuration, and gives you the numbers you care about (usage, limit, remaining credits).
• Make sure a key hash is stored in the Vault. The openrouter_key_info action relies on a keyHash being present. If it's missing, the call will fail.
• Your API key is never exposed. All responses mask the actual key value. You can safely share the output with support or in bug reports.
• All actions are read-only. Nothing you do with this tool can modify your account, change your key, or alter backend settings. It's safe to explore freely.
• Use health for quick diagnostics. If something seems off with your Yukkai setup, checking Cloud Code health is a good first step to rule out backend issues.