FAQ
The questions people actually ask.
Mostly about where data goes and what happens when something breaks. Both are fair.
Privacy
- Do the browser tools send my data anywhere?
- No. The 268 browser tools run entirely on your machine — the input never leaves it, so there is nothing for us to store, log or lose. A small number of tools are network-live by nature: a DNS lookup or a certificate check has to reach the internet to answer at all, and those are labelled.
- What about the API?
- An API call necessarily sends its input to us so the tool can run. We record what tool ran, when, and what it cost — not the payload. Automation output you asked us to keep is stored in object storage and deleted on the retention schedule your plan sets.
- Can I use this with data I am not allowed to share?
- Use the browser tools, which never transmit it. That is the entire reason they exist rather than everything being an API call.
Credits and billing
- How does pricing work?
- Credits. Every tool has a price in credits, and you spend from a balance rather than a subscription tied to a seat. Buying credits is a purchase, not a recurring charge you have to remember to cancel.
- What happens if a call fails?
- You are not charged. Credits are reserved before the work runs and returned if it does not complete — an AI provider timing out costs you nothing.
- Do credits expire?
- Purchased credits carry their own clock from the date of sale, and the remaining life of every batch is visible in your dashboard. Nothing disappears without a date you could have seen.
- Can I cap what an automation spends?
- Yes, per job, per month. Reaching the cap pauses the job and emails you rather than continuing quietly.
Teams
- Whose balance pays for a team's work?
- The organisation's. When you have an organisation selected, its wallet pays — never your personal balance. Usage records which member spent what.
- Is there a per-seat charge?
- No. You pay for work done, not for how many colleagues have an account.
- Can I limit what a member can do?
- Yes. Permissions are per member per workspace, covering keys, billing, automation and membership itself.
The API and automation
- How many tools are on the API?
- 230, plus 12 super tools in the browser — 221 altogether. One key reaches all of the API ones, and the same key works in the packages, the editor extension and the MCP server.
- Can a scheduled job run twice by accident?
- No. Each firing carries its own run id, and that id is the primary key of the run record, so a redelivered message cannot execute a second time however the infrastructure behaves.
- If a step fails halfway, do I pay for the whole thing again?
- No. A pipeline's fetch stage is persisted, so retrying a failed model step reuses pages you have already paid for rather than fetching them again.
- What happens when I revoke a key?
- It stops working immediately. There is no cached grace period.