Build actions

Building through the connector does not spend Floot credits — the thinking is paid for by your Claude, ChatGPT, or other AI subscription. What Floot meters is the work its own infrastructure does, and the unit is a build action. Generating images is the one thing that also spends credits, covered below.

What counts as one build action

One tool call your assistant makes to Floot is one build action. Reads count the same as writes: listing files, reading a file, running a typecheck, writing code, running SQL, publishing. Any call keeps your project's build machine awake, which is what the meter is really tracking.

Two things never count: failed calls and cancelled calls. A build that goes wrong and retries is not charged for the failure.

Tools that are never metered

Six tools are exempt, so an account that has hit its limit can still check on work in progress, stop it, and free up a published slot. Floot's own limit message names them:

Status polling (get_job_status, get_publish_status), list_projects,
get_preview_url, cancel_request, and unpublish_app are not metered and
still work; other tools are paused until the reset. Failed and cancelled
calls are never counted.

Everything else is metered, including orientation reads like get_guides and list_files. Any tool Floot adds later is metered unless it joins that list.

How many you get

Your day is 24 hours starting at a fixed hour, set when your account was created (the hour you signed up, so resets are spread across accounts rather than all landing at one moment). It is not midnight where you are, and it does not follow daylight saving. Plan & usage shows your reset time in your local time, and every limit message from your assistant states the exact instant.

The daily limit is the only one. There is no weekly cap on any plan, so every day starts with the full allowance whatever you used the day before. Unused actions do not carry over.

Build actions are not credits

Floot has two meters and they do not convert into each other.

Build actions

What your AI assistant spends when it calls Floot through the connector. They refill daily and are the meter for connector work.

Credits

What image generation spends, and what the AI features inside your own published app spend when people use it. Paid plans include a monthly credit grant.

One connector tool crosses over. generate_image writes AI images into your project and spends credits as well as a build action. Those credits are billed to the project owner's account, not to the account driving the chat — so generating images in someone else's project spends their credits. The AI features inside a published app bill the same way: off the app owner's account, whoever is using the app.

If you are on an older Floot plan

Plans on the older credit ladder buy credits, not build actions, so over the connector they are metered at the free limit of 100 a day. That catches people out — you are paying, and still getting the free caps. Switching to Pro or Power moves you onto action-based limits. The switch page at https://floot.com/dashboard/billing/switch shows exactly what switching would mean for your account before you commit.

When you hit the limit

Two things happen at the same time.

• Your assistant gets a refusal instead of the tool result. It names the limit you hit, says when it resets, and carries a plain Floot URL. The URL is deliberately plain text rather than a link — links get flattened when a reply is copied into an email, and users were left with nothing to click.
• If you have the project open in a browser, Floot surfaces a prompt there too, so the message does not depend on your assistant relaying it.

The six unmetered tools keep working, so your assistant can still poll a running build, cancel a pending request, and take an app offline while you are capped.

Your current plan and its allowances are on the plan page.