Tell any website what to do. …or just
point at it

A credit is one Standard AI request. Asking Flexbot for a new flex, or asking it to change one, uses 1 credit. A script that calls the AI while it runs (flex.ai(), for things like “summarize this thread”) uses 1 credit per call, for up to about 30,000 characters of input.

Failed requests are never billed. If a brand-new script throws an error on its first run, one automatic “Fix it” retry is free.

Smart sends your request to a stronger AI model. It's slower and uses 5 credits instead of 1 credit, and it's worth it for multi-step automations, fiddly sites or a script that didn't come out right the first time. Most tweaks and exports are fine on Standard.

Running your saved flexes, as often as you like: on page load, on demand or on a schedule, as long as they don't call the AI while they run. Editing code by hand, switching flexes on and off, deleting, exporting and importing are free too.

When your trial ends without a plan, your saved flexes keep running. Only the AI features stop, and scripts that use flex.ai() get a polite error instead of an answer.

Flexbot runs your scripts with Chrome's official userScripts API, the same one userscript managers use. Since Chrome 138, each extension that uses it needs your one-time permission: go to chrome://extensions, click Details on Flexbot, and switch on Allow User Scripts. Flexbot's setup screen takes you there.

Chrome then warns that the extension “will be able to run code which has not been reviewed by Google”. That's true of any userscript: the code is yours, written when you asked and saved only when you said so.

Desktop Google Chrome 138 or newer, on Windows, macOS, Linux or ChromeOS. Chrome on phones doesn't support extensions. Other Chromium browsers may work if they support the userScripts API, but we only test Chrome.

Here's how Flexbot keeps you in control, honestly stated:

• You see it before you save it. Every draft comes with a summary, the sites it runs on and a list of what it can do (“change how this page looks”, “save files”, “send page content to Flexbot AI”), plus the full code.
• Network is blocked by default. Scripts run in Chrome's user-script sandbox with network access blocked for their own requests. A script that needs the network must be approved by you, and only for the sites it names.
• Risky code needs your approval. Network use, reading cookies or site storage, touching password or payment fields, building code from strings, and obfuscated code are flagged before anything runs.

What it can't promise: a script you approve can still change the page it runs on, and a page-level trick like inserting an image can still reach the internet. Read the review card, and don't approve code you don't understand on sensitive sites like your bank.

Only when you ask Flexbot to create or change a flex: your prompt, the page URL without its query string or fragment, the page title, a compact text outline of the page, the HTML of the element you pointed at (with query strings and tokens redacted), the names and descriptions of flexes already on that page, and, when you're changing a flex, its code. Form field values and password fields are never included.

It goes to our server and our AI provider, Anthropic, to produce the result. Our server keeps only billing metadata (credits, token counts, timestamps), not prompts, page content or code. With your own key, it goes straight to Anthropic and never touches our server. Details in the privacy policy.

No. Flexes live in chrome.storage.local on the computer where you made them and are never uploaded or synced. To move them, export from the Library (as a Flexbot bundle or standard .user.js files) and import on the other computer.

On regular web pages, yes: shops, news, docs, dashboards, forums, web apps. Chrome doesn't let any extension run on its own chrome:// pages or the Chrome Web Store, and some apps that draw everything on a canvas (or block scripts very aggressively) are hard to change.

Flexbot also won't write scripts that get around paywalls or log-ins, download copyrighted media, post or send messages without asking you first, or grab time slots the moment they appear.

No. Scheduled flexes run on your computer, in a background tab, while Chrome is open. If Chrome was closed when a check was due, it runs once when Chrome starts again. Schedules can be as often as every 15 minutes, or every 60 minutes for scripts that use the AI.

Open Flexbot's Plans & billing and choose Manage billing to cancel in Stripe's customer portal. Your plan stays active until the end of the period you've paid for, and your saved flexes keep running afterwards.

If something went wrong, like a charge you don't recognize or a plan that didn't work for you, email hello@flex.bot and we'll sort it out. The terms have the details.

Not yet. Each person needs their own account or their own API key. You can share flexes by exporting them and having colleagues import them; imports always arrive switched off until they're reviewed.

In Flexbot's settings, choose My Anthropic key and paste an API key from your Anthropic account. Flexbot checks it, then sends every AI request directly from your browser to Anthropic. No Flexbot account and no credits to buy; only the safety limits on scripts (like the daily AI cap per flex) still apply. The key stays in the extension's private storage on your device.

You pay Anthropic for what you use. At Anthropic's prices in October 2026, a typical Standard request costs roughly 1–3 cents, a Smart request roughly 5–15 cents, and an AI call made by a running script usually under a cent. Check Anthropic's pricing page for current rates.

Yes. The whole project (extension, server and this website) is MIT-licensed on GitHub, and the Chrome Web Store build is made from that repository. You can run the server yourself with Docker and billing turned off, then set Flexbot's Custom server URL to it. Or skip a server entirely with your own key.