Score Studio
Documentation

Workspace · Plans and spend

Manage billing and usage

Understand plan allowances, managed AI capacity, usage, payments, and invoices.

Source reviewed 2026-09-16. Availability depends on your installation, permissions, and compatible runtimes. A supported path is not a guarantee of model quality or production readiness.

Outcome

Keep production work funded without making cost or renewal state surprising.

Start here

What you need to know first

Check the inputs below before starting. If you are new, begin with the first-project guide. A dataset holds media and labels; a model produces results; a deployment makes a selected model version callable. Creating one does not create the others.

Bring these inputs

  • Subscription and payment state
  • Metered workload and compute events
  • Card or native TAO payment identity

Expected output and limits

  • Credit balance, usage ledger, invoices, and payment state
  • Plan or prepaid-credit changes

Core workflow

01

Review the plan

Free is $0 for one small private workflow. Smart is $69 per month and adds cloud-based production APIs, agents, and a 48-hour email response target. Pro is $249 per month with higher limits, customer-owned providers, hosted endpoints and agents, Score-operated infrastructure, and a 24-hour email response target. Community is a separate Apache 2.0 installation that runs locally on infrastructure its operator supplies. Open Billing to inspect the active plan, renewal date, and managed AI allowance for the selected workspace. Opening the page does not start a purchase.

02

Understand usage

Review API requests, evaluations, and managed AI use for the current month. Each plan includes a monthly number of production API requests and evaluations; past it, new ones are refused until next month or an upgrade. Nothing is billed beyond the plan.

03

Manage payment

Pay the fixed monthly fee by card or native TAO; direct SN44 alpha payments are coming soon. Paid features activate after the first payment settles. Card subscriptions renew through Stripe; TAO subscriptions renew when the available settled balance covers the next month. Open the Stripe customer portal for payment methods, billing details, and invoices. A TAO payment address is provisioned by the payment service rather than by the console, so a new workspace can see the address as not ready yet for a short moment; retry shortly. Native TAO transfers fund the workspace only once they are final on the network. Their USD credit increases Managed AI remaining, including on Free. Unspent TAO-funded credit carries across renewals; AI usage and wallet-funded subscriptions reduce it.

04

Add managed AI capacity

Smart and Pro can buy fixed $50 capacity packs for additional Fast or Ultra usage until the normal renewal date. A Score capacity voucher adds the same pack at no charge. Workspace owners and admins redeem it in Billing. Managed AI stops at zero and never creates automatic overage.

What this surface supports

Free, Smart, and Pro plan state

Included and purchased managed AI capacity

Complimentary capacity voucher redemption

Usage history

Card and native TAO payment paths, with SN44 alpha coming soon

Expert section

Contracts, signals, and failure modes

Use this section when you are defining acceptance criteria, automating the surface, or reviewing whether its output is safe to promote downstream.

Quality and operating signals

  • Remaining and forecast credits
  • Renewal/reset date
  • Payment status
  • Spend by workload type

Common failure modes

  • Exhausting credits during critical work
  • Failed payment method
  • Treating provider spend as included Score credits

Expert release checklist

□ Inputs and dependencies are pinned to immutable versions.

□ Acceptance metrics include critical classes and operating slices.

□ Failure, retry, cost, and rollback behavior are understood.

□ The resulting artifact has an owner and a downstream review path.

Engineering safeguards

  • Renewal and reset dates stay visible
  • Plan changes are explicit
  • Usage limits surface before blocking
  • API requests and evaluations stop at the included monthly quantity; nothing is billed past it
  • Refunds and disputes, on subscription fees too, are booked against the wallet, never left as silent drift
  • A card top-up counts only once its settlement is booked to the ledger; until then the console says it is crediting rather than showing a balance that has not moved

Continue in Score

Open the productOpen Billing & usage
Manage billing and usage · Score Studio