Wallie Cloud: email alerts when your agent goes offline
Wallie Cloud receives decision events and heartbeats from connected Wallie agents. It runs outside your agent’s machine, so it can detect silence when that machine is asleep, offline, or stopped.
€20 per month, per workspace
- A shared feed of payments, blocked attempts, approvals and Solana channel events.
- Email rules for selected events, agent silence, recovery and unresolved escrow.
- Workspace keys, sign-in links, and billing management.
- Multiple agents per workspace. Wallet signing remains in your infrastructure.
Subscribe to Wallie Cloud Sign in
Connect an agent
Use the workspace key from your welcome email:
npm i -g allowance-kit export WALLIE_CLOUD_KEY="<your workspace key>" allowance-kit notify cloud "$WALLIE_CLOUD_KEY" allowance-kit notify test
The cloud test checks that your key connects. To verify email, sign in to Alerts, add a rule for silent and back, and send a test. Keep the same state directory and agent name across your setup and runtime commands.
How heartbeat monitoring works
A running connected agent sends a heartbeat every 60 seconds. The default silence threshold is five minutes, and the hosted watchdog checks once per minute. A heartbeat after silence creates a recovery event. Delivery depends on the configured rule and email provider; test the inbox before relying on it.
What the product controls
The open-source runtime checks allowances before signing supported x402 payments on Base, Base Sepolia and Solana. Solana supports fixed price exact payments and metered upto channels. Public Solana payment evidence is from devnet. Cloud monitors the decisions the runtime sends. It does not sign payments, enforce policies remotely, or cap existing metered OpenAI, Anthropic, or cloud-provider invoices.
Data and cancellation
Events and associated delivery records expire 90 days after receipt. After cancellation takes effect, they are deleted after 30 days, or sooner under their normal retention period. Billing records have separate retention requirements. See Privacy and Terms for details.
Cancel through billing management or contact support. Access continues through the paid period, followed by a seven-day ingestion grace period after cancellation takes effect. The first month has a 14-day refund policy as described in the terms.
Start with the free runtime
Follow the practice-money tutorial or inspect the source on GitHub. Cloud is optional; local spending limits work without a subscription. Read the x402 spending limits guide for a concrete $5 allowance example.