The usage chart whose 700 is fiction
An MIT skill that shares Grok bot usage, with the sample labeled as not an account.
- Category
- Developer tools
- Who it is for
- Someone whose Grok bots already hit a weekly limit and cannot see which routine did it.
- Possible model
- Open source
- Difficulty
- Medium
- Inspired by
- Botburn · Botburn
- Original launch
- Watch the launch · Nov 5, 2026
Difficulty is an editorial estimate of technical and operational complexity, not a score.
Startup idea analysis by Startup Ideas. Last reviewed Nov 6, 2026. How we read a launch.
The startup idea
Thomas posted Botburn on November 5. His Grok bot hit 90% of the weekly limit by Tuesday, so he built a free skill that shows which bot, which routine, and which day burned the usage. He says OnlyBots was replying to fans 700 times a week. The repository is apwn/botburn. The license is MIT, 2026. Version 0.1.0 is an early public kit: a skill, docs, and a synthetic sample. It is not a GitHub release until review, and the readme says it is not an official product. The pictured audit is labeled fiction, not a real account. The sample write-up uses about 700 runs a week as example language for a site heartbeat. Figures are shares of all Grok Bot usage in the window unless the report says it renormalized. The post reads like a measurement of one bot. The repo's 700 is the sample. This page did not open an account.
The opportunity is the share of a real window, not the picture in the readme. A smaller product is one week, the global denominator, and the fiction label on the sample. A dashboard that presents the sample as the user's week is not this kit.
Do not quote the sample as a customer. Do not call it an official Grok product.
The problem
A weekly limit is gone by Tuesday, and the bill does not say which routine did it.
Who would pay for this?
- Primary
- Someone whose Grok bots already hit a weekly limit and cannot see which routine did it.
- Secondary
- A person who will read the fiction label before repeating a number.
- Early adopter
- One real window, shares of all usage, the sample marked fiction.
How could it make money?
Possible models. Nothing here is a claim about what Botburn charges.
- No price. MIT.
- Not an official product.
- The post says free.
What would the MVP look like?
- A skill.
- Shares of a real window.
- The sample labeled fiction.
- Early status printed.
How to validate the idea
- Ask five people whether the 700 was their account.
- If they say yes, they missed the fiction line.
- Do not ship the sample chart as a report.
How to differentiate
- It is a skill, not a hosted bill.
- The picture is fiction.
- The denominator is all usage.
- Do not become the bot.
Original product launch
This launch is inspiration and evidence that someone shipped, not a partnership. The idea above is our reading of the broader opportunity. Botburn did not write it.
- Product
- Botburn
- Source
- Botburn
- Film
- Botburn, the 700 is a sample
- Posted
- Nov 5, 2026 · 0:28
Product that inspired this idea
Thomas's post says his Grok bot hit 90% of the weekly limit by Tuesday, so he built Botburn, a free skill that shows which bot, routine, and day burned the usage. He says OnlyBots was replying to fans 700 times a week. The repository is apwn/botburn. The license is MIT, 2026. Version 0.1.0 is an early public kit: a skill, docs, and a synthetic sample. It is not a GitHub release until review, and it is not an official product. The pictured audit is labeled fiction, not a real account. The sample write-up uses about 700 runs a week as example language. Figures are shares of all Grok Bot usage in the window unless the report says it renormalized. The post reads like a measurement. The repo's 700 is the sample. This page did not open an account.
Posted by @ThomasKanze. Watch the original launch. No separate product site is listed unless the post itself is the source.
- agents
- usage
Related startup ideas
- A drive that files the document and cites the page
Upload a pile of files, have them land in a folder a person would recognize, and answer a question with the page it came from.
- A visible team of agents in a world you can walk into
Use a shared world, not a log file, when several agents need a person to come over and decide.
- An Android remote for coding agents
A phone client for checking projects and steering agents when the laptop is closed.
- An inbox so the agents stay quiet
Collapse every coding-agent thread into one list, and only interrupt when one of them is stuck.
- Coding agents in the menu bar
Show which coding session is working, which is stuck, and let a person reply without opening the app.
- Cut the launch film from the app you already have
A skill that rebuilds the screens in a frame, times them to a track, and renders on the machine the coding agent already uses.
Looking for more ideas?
The full list is startup ideas for 2026, each one tied to a launch you can watch.
Browse startup ideas for 2026