Braio

Costs and plans

Czytaj po polsku

Braio - costs, limits and billing principles

Agent work costs depend on tasks, model usage, available integrations and rollout scope. Confirm terms for your workspace and process before starting.

This page explains how to assess costs. It does not publish an unconfirmed tariff or promise unlimited usage. Confirm the current offer and limits with the Braio team.

Content reviewed:
01

Before the first financial report run

The template page offers synthetic files and a method description without an account. This does not mean every in-app process is free. Check feature availability, document limits and the applicable workspace billing terms before starting.

A starter prepares a screen or task draft. It does not approve the profile or automatically launch paid work. Include failed attempts, revisions and your review time when assessing cost; the local technical pack is not a customer savings measurement.

02

What the offer needs to cover

Platform access, usage for executing a task and deployment services are different components. Confirm their availability and billing method in the current offer.

  • Users and features included in the plan.
  • Model usage, task runs and required execution resources.
  • Integration setup, process preparation, support and organization requirements.
03

Compare the cost of a specific workflow

Start with one repeatable task and agreed quality criteria. Measure execution cost, review time and the number of useful results. This is an assessment method, not a savings calculation or a return-on-investment promise.

The price of a single model response does not automatically cover the complete process. Retries, additional steps and human review can change its economics.

04

Limits and cost consent

Check your workspace's limits and consent rules. Operations do not all have the same conditions. Access to an agent catalogue does not mean unlimited use of every tool.

For example, an SEO/GEO report accepts up to 10 URLs with one active report per workspace. These feature limits do not replace plan and billing terms.

05

Prepare a scope for the discussion

Describe the first process, user count, tools and expected run frequency. Include access, support and security requirements so the discussion concerns an actual use case.

  • What result should the agent deliver and how will you review it?
  • How often should the task run and which integrations does it need?
  • What control, deployment and support requirements apply?

Questions and answers

Can I rely on a price from an older document?
Confirm terms in the current offer for your organization. This page does not replace an agreement or the plan information shown in your workspace.
Is usage unlimited?
We do not promise unlimited usage. Feature availability, limits and execution costs depend on the current terms and configuration.