$180K in 5 Days with OpenClaw

I was living in the future.

For the last year, I've been deep with Agentic in my profession, helping customer innovate and accelerate. For the last few months, I'd been deep in the weeds with OpenClaw, watching it grow from good to beyond great — testing models, building agents, automating my entire digital life. I watched Anthropic do an about face on people using their Max subscription for OpenClaw. I'd burned through $150 on Claude Opus in what felt like seconds. Sonnet was good, but lacked so much compared to Opus 4.5 and then 4.6. OpenAI was just as expensive, so I pivoted. Found Chinese models were dirt cheap, but I didn't want my data farmed. Enter Kimi-K2.5: open-weight, AWS-hosted, pennies on the dollar, scored as high or higher than Opus in various open metrics, and my data stayed in my account where it belonged.

I built Coder — an agent powered by OpenAI's free Codex demo that handled my heavy lifting without costing a dime. Then Research Bot, endlessly collecting information while I slept. I created a command center to watch them all: cron jobs firing, agents humming, usage climbing in neat, predictable lines on my OpenClaw dashboard.

It was magic. I'd hooked OpenClaw to my email (read-only, of course) and it started drafting responses from memory. Gave it read-only access to my code base for nightly reviews. I was operating at a level I didn't think possible — one guy with an army of digital workers, all perfectly coordinated.

How can my wife use this? Friends? I need to make this easier to scale. (Hey, I'm Amazonian). The average person would never set this up. Too technical, too complex. So I started building — a platform where anyone could spin up their assistant in ten minutes. I was working 9 PM to 1 AM for months, after putting my kids to bed, after AWS work ended. My marriage was taking a back seat, but I told myself it was temporary. Just until I got this right.

Then, on February 25th, I logged into AWS.

The Cost Explorer graph that normally sat at $100–$125 had a spike that looked like a heart attack on an EKG. $159,000.

I stared at it. Logged out. Logged back in.

Still there.

My hands went cold. My stomach dropped through the floor. I clicked deeper — Bedrock usage. 24 billion tokens in a single day. Nearly $70,000.

The math didn't compute. At that burn rate, my annual run rate was $30 million. My one little VM couldn't process 40 million tokens per minute. This wasn't me. This was... something else.

Did the research bot spiral into an infinite loop? Did I leak my Bedrock API key? What else was compromised?

OpenClaw had access to my email. My source code. My entire digital life. I thought I'd hardened everything — read-only permissions, no downloaded skills, code reviewed by a separate bot before deployment. Was I compromised? Were both bots compromised?

I dug into CloudWatch. Empty. The Bedrock logs had stopped right when the chaos started. No traces. No explanations. Just $160,000 of phantom debt and a silence that felt almost intentional.

I turned everything off. OpenClaw. Bedrock. Every agent, every cron job, every connection I'd spent months building. I was convinced my API key had been stolen, that I'd leaked everything, that my two decades of perfect credit were about to evaporate.

I couldn't breathe properly. My heart was hammering like I'd run a marathon. I stayed up until 4 AM hunting for logs, for evidence, for anything that would explain what I'd done wrong. I had to tell my wife. I had to explain that I'd ruined us financially while she'd been asleep next door, trusting I knew what I was doing.

The AWS support page had no phone number for my tier. I filed a ticket into the void. Waited a day. Nothing. Logged back in: $180,000. A 141,000% increase on my normal bill.

I submitted another ticket. Found a callback option. When the phone rang, I bumbled through the conversation with a colleague who didn't know I was an AWS employee myself. “I don't know what happened. I can't pay this. I need help.” It hurt to say out loud. I thought I was technical enough to avoid being another Reddit horror story. I'd hardened everything. I'd been careful.

Three more days of silence. No email. No update. No “hot new customer” alert triggered by my $70K/day burn rate. I gave the ticket a Bezos “?”

Then, finally, a response. Londani from AWS Premium Support:

“There is an ongoing issue affecting the billing for Bedrock models on the mantle endpoint. The root cause has been identified on the service side... No action is required from customers at this time. We apologize for the inconvenience caused.”

Inconvenience.

I read that word three times. Inconvenience. I'd spent nights troubleshooting in panic. I'd had conversations with my wife about financial ruin. I'd questioned my own security practices, my technical competence, my ability to protect my family. I'd aged five years in five days.

But it wasn't me. It was never me.

I realized two things that week about Agentic tools such as Openclaw...

I wish this hadn't happened to me. It took months — maybe years — off my life. I've never felt so defeated, so helpless, so convinced I'd destroyed everything I'd built.

But that note from AWS Support, confirming it wasn't my fault... it did something unexpected. It lit a fire. If a technically sophisticated user — someone who works at AWS — could almost have a heart attack over phantom billing, what about everyone else? The non-technical users who just want to automate their lives? They're one billing glitch away from the same panic I felt. FWIW -- Total billed was ~150USD for the month.

I'm more motivated than ever to get my platform out there. To give people the guardrails I wished I'd had. To make OpenClaw accessible without making it dangerous.

The future is agentic. But it needs to be safe first.