> For the complete documentation index, see [llms.txt](https://docs.protoboard.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.protoboard.xyz/protobot/usage-and-energy.md). # Energy and usage How ProtoBot Energy (Wh) is counted, what uses more of it, how to get more out of it and what happens to your data ## Energy (Wh) ProtoBot usage is measured in **Energy**, using **Watt-hours (Wh)** as a themed credit unit. Wh is a product credit unit within Protoboard; it does not represent literal electrical power. Every plan includes a daily Energy allowance: **500 Wh on Free** and **1,000 Wh on Pro**. The allowance is a rolling 24-hour window that opens with your first message. The **battery** in the ProtoBot panel shows what's left; click it to open **Settings > Plan**, which shows the remaining Energy and when the window resets. When Energy runs out, ProtoBot pauses until the window resets; the rest of Protoboard (canvas, parts library, DRC, BOM, sharing) keeps working. **Bonus Energy** from coupons never expires and is used only after the daily allowance runs out. See [Bonuses and coupons](/account/bonuses-and-coupons.md). Calls from external agents through the [Agent Bridge](/agent-bridge/overview.md) don't use Energy.
The battery indicator in the ProtoBot panel showing the percentage of Energy left

The Energy battery.

### What uses Energy Four things drive cost: 1. **Model choice.** More capable models cost more per interaction. The model menu shows each model's price. See [Models and reasoning effort](/protobot/models-and-reasoning.md). 2. **Reasoning effort.** The reasoning-effort control next to the model selector sets how much the model thinks before acting. Higher effort handles hard problems better but uses more energy; Medium is the default, and Low or Off keep routine work cheap. 3. **Mode.** **Concept** skips web and datasheet research, so it uses less than **Integrate**. See [Modes](/protobot/modes.md). 4. **Task size.** A short question ("What's on my board?") costs little; a multi-step workflow ("find a regulator, place it, wire it, run DRC") chains many tool calls and costs more. ### Getting more out of your Energy * **Stay on the default model** for routine tasks; switch up only for genuinely complex workflows, and switch back after. * **Combine related actions** into one message: "Create a harness, auto-link interfaces, and run DRC" costs less than three separate exchanges. * **Be specific.** One well-constrained prompt replaces several vague back-and-forths. See [Prompt patterns](/protobot/prompt-patterns.md). * **Use auto-link and auto-allocate** instead of wiring connections one at a time. * **Start a fresh session when switching topics.** Long sessions accumulate context that must be processed with every message. *** ## Data and privacy Using ProtoBot means your design data flows through an AI provider. Here is exactly what that involves. ### What gets sent When you message ProtoBot, the request to the model includes your **board data** (parts, interfaces, harnesses, allocations, BOM, name, notes, requirements, tasks) and your **conversation** (messages, responses, tool inputs and outputs). There is no way to use ProtoBot without sending board data to the AI provider. ### Where it goes ProtoBot's models are provided by **OpenAI**, so requests are processed by OpenAI's API servers. Sessions and messages are also stored by Protoboard so your history persists. For provider-side handling, see [OpenAI's API data usage policies](https://openai.com/policies/api-data-usage-policies). ### What not to include {% hint style="danger" %} Never paste credentials, API keys, or passwords into the chat. They would be sent to the AI provider and stored in your session history. {% endhint %} Also avoid: personally identifiable information about end users, trade secrets, regulated data (HIPAA, ITAR, EAR), and financial details. Technical content (constraints, part numbers, protocols, pin mappings, BOM data) is what ProtoBot is designed for. ### Sensitive projects * **Typical prototypes:** component specs and connection topology are not inherently sensitive; focus your review on correctness rather than exposure. * **Proprietary designs:** use ProtoBot for the standard portions (power supplies, common sensor interfaces) and handle trade-secret subsystems manually. Check your organization's policy on third-party AI tools. * **Regulated industries:** designs under HIPAA, ITAR, ISO 13485, DO-178C, or similar frameworks may restrict third-party AI processing. Consult your compliance team first. The [Privacy Policy](/legal/privacy-policy.md) and [Terms of Service](/legal/terms.md) are the definitive documents governing data use. ## Related pages * [Plans, limits and Energy](/start-here/plans-limits-and-energy.md) * [Models and reasoning effort](/protobot/models-and-reasoning.md) * [Bonuses and coupons](/account/bonuses-and-coupons.md) * [Plan limits table](/reference/plan-limits.md)