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.
A Solana spending-account server, exposing 4 tools that pay an address or an x402-protected endpoint within limits the account itself carries.
- 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.
A Cloaked Agent key, supplied as CLOAKED_AGENT_KEY. Every tool also takes agent_key as a call argument.
One command plus a key — npm install @cloakedagent/sdk, then supply credentials