Boo Lab, Inc.
Usage, Billing, and Credits Terms
Version 0.2 • Last updated: June 5, 2026
These Usage, Billing, and Credits Terms apply to usage-based fees, credits, invoices, payment methods, and usage controls for Boo. They are part of the Master Subscription Agreement and Terms of Service.
Usage-based pricing
Boo charges based on usage unless an Order Form states otherwise. Usage may include model tokens, prompts, outputs, tool calls, model inference, embeddings, indexing, storage, compute, scripts, background jobs, app hosting, public web retrieval, connector activity, orchestration, third-party services, and other metered activity.
Pricing sources
Applicable prices may be stated in an Order Form, pricing page, usage dashboard, checkout page, invoice, or written quote. Boo may update prices according to the Agreement, pricing page, or applicable Order Form.
Model and tool optimization
Boo may optimize model and tool selection based on task requirements, quality, cost, latency, safety, and availability. Boo may use lower-cost models or tools when Boo determines they are appropriate for the task.
Usage records
Boo's usage records are the source of truth for billing unless Customer reasonably shows a material error. Usage records may include timestamps, workspace, user, feature, model class, token counts, tool calls, compute, storage, connector activity, and other billing metadata.
Invoices and charges
Unless an Order Form states otherwise, Boo may invoice monthly for usage incurred during the prior billing period, or charge a payment method at the time of usage or recharge for self-service accounts. Invoices may include Usage Charges, subscriptions, credits purchased, taxes, and other applicable fees.
Credits
Boo may require Customer to purchase or maintain credits. Credits may be consumed as Customer uses Boo. Credits are not refundable and have no cash value unless required by law or an Order Form states otherwise.
Exhausted credits
If Customer's credits are exhausted, Boo may stop, suspend, queue, or limit Services until Customer adds a valid payment method, purchases more credits, or enables automatic recharge.
Payment method
Boo may require a valid payment method. Customer authorizes Boo and its payment processor to charge the payment method for fees, Usage Charges, taxes, and other amounts due.
Auto recharge and spending caps
If Customer enables auto recharge, Boo may charge Customer when credits fall below the configured threshold. Customer may set spending caps where supported. Spending caps and alerts are intended to help manage usage but may not prevent charges already incurred, queued, or in progress. If a cap is reached, Boo may stop or limit usage until the cap is raised or more credits are added.
Failed payments
If payment fails, credits are exhausted, or an invoice is overdue, Boo may suspend or limit access, stop background jobs, disable high-cost features, or prevent additional usage until payment is restored or credits are replenished.
Taxes
Customer is responsible for applicable taxes except taxes on Boo's net income. Boo may collect taxes where required.
Billing disputes
Customer must submit billing disputes within 15 days after invoice date or charge date, as applicable. Customer must pay undisputed amounts on time.
No set model guarantee
Boo does not guarantee use of a specific model, provider, latency level, quality level, or cost level unless an Order Form states otherwise.
Usage by Authorized Users
Customer is responsible for usage by Authorized Users and usage through Customer's connected systems, tokens, workflows, background jobs, and apps.
Abnormal usage
Boo may suspend, throttle, limit, or contact Customer about abnormal usage, suspected abuse, credential compromise, unexpected spend, system error, or activity that could create excessive charges or service risk. Boo may, but is not required to, notify Customer of unusual usage before charges are incurred.
Usage estimates. Usage estimates, previews, budgets, alerts, or cost projections are informational only and may differ from actual charges.
Termination and final invoice
Customer remains responsible for Usage Charges incurred before termination or suspension, including charges from queued, background, or in-progress work.