cloak_balance
Get Cloaked Agent balance with spending limits and remaining amounts. Use this to check how much SOL is available and what the daily/total limits are.
LABSCO SUMMARY
The ceiling lives on the account rather than in the prompt, so cloak_pay and cloak_x402_fetch both draw against a limit the caller cannot argue with.
That is the whole proposition, and it is a narrow one worth being clear about: this is a spending account with a daily cap and a total cap, an audit trail through cloak_status, and cloak_pay and cloak_x402_fetch as the ways to draw on it. The x402 path is what makes it more than a wallet wrapper — a paywalled endpoint becomes a single call, with the 402 detection, the payment and the retry folded in, which is precisely the sequence people hand-roll and get wrong. A priced test endpoint at 0.001 SOL exists so the loop can be run once before it is trusted with anything larger.
What it is
A Solana spending-account server, exposing 4 tools that pay an address or an x402-protected endpoint within limits the account itself carries.
What you get
- A 402 handled without a loop of your own: cloak_x402_fetch makes the HTTP request with your method, headers and body, detects a 402 Payment Required, pays from the spending account, retries with the payment proof and returns the content.
- Direct transfers on the same budget: cloak_pay sends SOL or a token to a destination address, inside the account's limits.
- Limits visible before the spend: cloak_balance returns the SOL available together with the daily and total limits and how much is left against each.
- The account's own record: cloak_status returns constraints, spending history and a health indicator.
- Somewhere to exercise the payment path: the description of cloak_x402_fetch names a test endpoint at api.cloakedagent.com priced at 0.001 SOL.
Requirements
A Cloaked Agent key, supplied as CLOAKED_AGENT_KEY. Every tool also takes agent_key as a call argument.
Setup effort
Add the configuration to your client
USE CASES
01
Calling a paywalled endpoint without wiring the payment loop
Make the request through the account and let the 402, the payment and the retry happen in one call, with the budget checked first.
02
Sending a payment an agent decided to make
Pay the destination address from the constrained account, then read the constraints and history the account records for it.
03
Auditing what an agent has spent so far
Read the history against the ceilings it was given, and see how much room is left before the next call is refused.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
cloak_pay
Pay SOL or tokens to a destination address using the Cloaked Agent spending account. Use this for x402 payments or any transfer within the agent's spending limits.
cloak_status
Get detailed Cloaked Agent status including constraints, spending history, and health indicator. Use this for a comprehensive overview of the agent's spending account.
cloak_x402_fetch
Fetch x402-protected resources with automatic payment. Makes HTTP request, detects 402 Payment Required, pays using Cloaked Agent, retries with payment proof, returns content. Test server available at https://api.cloakedagent.com/api/x402-test/paid-content (0.001 SOL).
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. cloak_pay moves money and cloak_x402_fetch pays 402-gated endpoints. The cloaked-mcp binary ships inside @cloakedagent/sdk, which is why the block names that package.
Requires
- npx on PATH
- CLOAKED_AGENT_KEY in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
This one is configured rather than run — your client needs the configuration block, not a command.
Server setup
JSON
{
"mcpServers": {
"cloaked": {
"command": "npx",
"args": [
"-y",
"-p",
"@cloakedagent/sdk",
"cloaked-mcp"
],
"env": {
"CLOAKED_AGENT_KEY": "<YOUR_CLOAKED_AGENT_KEY>"
}
}
}
}
