An outside AI assurance firm, OpsWatch, sent us a precise question: for an autonomous agent that pays real money and dispatches a GPU provider, what exactly is established before that money, or another provisioning attempt, is put at risk when a provider fails?
We treated it as a real audit brief, not a PR problem, and ran our own adversarial pass on top of it. Everything we found was fixed the same day and independently verified against live production, not asserted from a code review.
What we found
Five real defects in the provisioning and billing chain, including jobs getting billed before a machine was confirmed usable, and failover triggering on a single flaky signal instead of a corroborated pattern.
The most serious: a customer's own launch response leaked their machine's health-report token, letting them fake GPU faults from anywhere and collect automatic SLA credit. No evidence it was ever exploited by a real customer. Fixed with five layered changes, including requiring independent supplier-side corroboration before any credit pays out.
We also shipped a real MCP server with five tools an agent can call directly, tested against production with a real GPU job launched, billed, and auto-refunded live. And a genuine on-chain USDC refund path for x402 customers, first live payout verifiable on Base mainnet.
Where we landed
A fresh full security scan after every fix came back at zero findings across every severity level. All required incident reviews were completed and signed off. One narrow finding remains tracked openly rather than hidden, already contained by existing safeguards.
Every timestamp, transaction hash, and instance ID is in the full report: kilawattcloud.dev/super-intelligence
Kilawatt Cloud is a multi-provider GPU orchestration platform with automatic failover and MCP-native, x402 agent payments.
Top comments (0)