Usage & Credit Limits: Best Practices

Understand how Functionize credits work, what happens at your limit, and how to get the most testing value from every credit.
Functionize usage is metered in credits. Agentic work, the AI-driven actions that create, run, and repair your tests, consumes credits. Routine account and review work does not. Every Subscription comes with its own credit allocation, and this guide explains how that allocation works and how to stretch it.

What consumes credits (and what doesn't)

Agentic actions consume credits. These are the actions where a Functionize agent does the work for you:

  • Creating tests
  • Executing tests
  • Diagnosing and fixing tests

Everyday actions do not consume credits. You can do all of the following without touching your allocation:

  • Manually editing existing tests
  • Viewing dashboards and reports
  • Managing integrations
  • Exporting results
  • Adding or removing users and other team/admin work

Rule of thumb: if an AI agent is doing the work, it costs credits. If you're reviewing, editing, configuring, or administering, it doesn't.

How credits work

Allocation

Each plan includes a set number of credits. Team plans (Growth, Scale) and Enterprise use a pooled allocation shared across the team. Individual plans identify per user allocation and are not pooled.

Billing cycle

Credits are billed on your plan's payment cycle monthly or annually, in advance.

Reset

Credits reset at the start of each billing period.

Credit Roll over

For monthly plans, credits do not roll over, they expire each month. For annual plans, all credits are pooled at time of billing and can be used by any user.

Mid-cycle add-on credits

Only available on select plans: Add-on credits purchased mid-cycle are available at any time for purchase, but similar to the original credit usage, add-on credits do not roll over.

Adding Users mid-cycle

New seats are charged at the agreed upon rate in your Order Form or online purchase agreement. If purchased midcycle, You will be charged a prorated amount and receive a prorated number of credits for the remainder of the cycle.

Where to see usage

Admins can view credit usage in the Studio sidebar and in Reports at any time.

Tip: If your monthly usage varies, an annual plan will typically be the better value. You get all 12 months of credits upfront and can draw against them as your testing needs ebb and flow. 

What happens when you run out of credits

Running out of credits does not lock you out of your account or your data. Here's exactly what changes:

Blocked until you have credits again:

  • Any action that requires an agent: creating, executing, or diagnosing tests.

Still available with no credits:

  • Manually editing existing tests
  • Viewing dashboards and reports
  • Managing integrations
  • Exporting results
  • Team and admin work

Active customers always retain access to existing data in accordance with the Functionize data retention policy.

To restore agentic actions, You can wait for your next reset, upgrade your plan, or purchase add-on credits on an ad-hoc basis.

Getting the most value from every credit

Following these practices are not required, but are to help guide you to ensure you get the most testing coverage from your plan while keeping credit consumption efficient. 

1. Be specific in your instructions

The more precise your instructions when generating a test, the fewer iterations the agent needs. Every re-generation costs credits. For example, instead of asking Functionize to "test the login page," give the agent intent and verification points, "Perform login at https://example.com/login with the provided credentials. Verify the dashboard loads and the welcome message appears. Then log out and confirm return to the login screen."

Clear intent means the agent will be able to achieve your goals in fewer generations.

2. Reuse common flows with Components

For workflows you repeat everywhere, such as login, navigation, checkout, it is most efficient to convert them into Components. Instead of regenerating those steps in every test, a single Component is authored once and reused across every test that references it. Credits spent once; value multiplied. The agent can help you take this step as well.

3. Let the agent fix, don't start from scratch

When a test breaks after a UI change, use the fix/diagnose path rather than regenerating the whole test. The Functionize agent applies targeted fixes, such as timing, element identification, and individual steps, at a fraction of the cost of a full re-generation.

4. Batch non-urgent fixes

After an app update breaks several tests, let the agent work through them in sequence rather than regenerating each one.

5. Use Orchestrations for scheduled runs

Set up an Orchestration for your regression suite and schedule it during off-peak hours. Orchestration execution is efficient and gives you consolidated reporting across all tests in a single run, avoiding per-test trigger overhead. Keep your plan's concurrent-run limit in mind when sizing a suite.

6. Monitor and prune

Periodically review tests that haven't run in a while. If a test covers a feature that no longer exists or has been superseded, archive it. Every stale test left in a scheduled orchestration burns credits for no value.

Billing Issues

If a payment fails. A failed renewal payment will result in your account being marked as the subscription past due. Your remaining credits will stay intact and you will keep read and admin access, but new agent work will be blocked until payment issues or delays are resolved.

If you cancel. Cancellation for enterprise agreements is subject to the terms and conditions of your order form. Cancellation of your monthly plan can be done at any time and will result in loss of access at the end of that cycle and will no longer be renewed. Cancellation mid cycle does not result in a refund or proration of credits.