AI Credit Consumption Policy

Version 5.0.0

Effective date: August 1, 2026

This policy explains which artificial intelligence activities are included in the contracted access, how Autopilot executions are metered, and how AI Credit balances, replenishments, and validity periods work.

Ordinary interactive use of Copilot, when contracted, is included and does not consume AI Credits, subject to fair use. Work delegated to Autopilot is metered based on dynamic consumption or a fixed price for a predefined unit of work. Workbench is the environment in which the Customer monitors, guides, and reviews these executions.

1 Applicability and access rights

This policy supplements the Order, the Terms of Use and License, and the applicable Product Terms, subject to the order of precedence by subject matter. It applies to products and channels that use the Looplex AI Account, in accordance with the contracted rights.

Access to Copilot, Workbench, APIs, MCP, models, profiles, and workflows depends on the offering. Purchasing credits does not automatically enable features or products, and an access license does not, by itself, include a credit balance or unlimited executions.

AI Credits are commercial units of consumption. They do not necessarily correspond to tokens, hours, documents, or a single monetary value. They are also distinct from Professional Services Credits, SLA service credits, and money, and are not convertible among these categories unless expressly provided otherwise.

2 AI Account and responsibility for consumption

The AI Account holds the organization’s balance, which may be used across eligible products and channels. Allocating permissions and limits among users, teams, applications, or integrations does not, by itself, create separate commercial wallets.

Consumption by authorized users, administrators, agents, service accounts, and integrations is attributed to the corresponding organization. The Customer is responsible for determining who may initiate work, purchase credits, and authorize overages.

Sharing the balance does not expand licenses, permit transfers to third parties, or combine accounts belonging to different organizations into a single contractual arrangement, unless expressly provided otherwise.

3 Included Copilot use and fair use

Copilot provides interactive assistance within the available and authorized system context. Depending on the contracted features, included use may encompass queries, information retrieval, explanations, summaries, targeted comparisons, assisted drafting, and expressly authorized simple actions, such as updating a field.

Frequent or intensive human use does not, by itself, constitute abuse. Fair use takes into account the interactive nature of the activity, the capacity of the offering, and security rules. Automation at scale, machine-to-machine use, and attempts to use Copilot as a continuous processing mechanism may be subject to separate limits or contractual arrangements disclosed for the applicable channel.

To manage the capacity, performance, and costs of included use, Looplex may, at its discretion, dynamically select, switch, or replace the models serving Copilot on a per-user or per-organization basis, including based on the volume, frequency, concurrency, or intensity of use, even when such use is legitimate. This management may involve lower-cost or less capable models and may vary over time, without prior or individualized notice, additional confirmation, or an indication of each change in the interface.

The continued use of a specific model, provider, or configuration is not guaranteed unless expressly committed to in the Order. These adjustments will comply with the expressly contracted features and conditions and with security and data protection obligations. The absence of a notice requirement for each model change does not eliminate communications required by contract or law for other changes.

Included use does not encompass the delegation of persistent execution chains, batch processing, ingestion and structured extraction of new documents, scheduled routines, or event-triggered work. These activities are part of Autopilot when offered. Native Copilot uses the context already available; preparation of new documents for processing is governed by the corresponding intake and execution feature.

Looplex may apply the rate, concurrency, and capacity limits provided for the offering, as well as safeguards against abuse. These controls do not retroactively convert an included interaction into billable Autopilot consumption.

4 Autopilot and execution authorization

Autopilot performs delegated work, such as processing documents, extracting data, preparing a legal filing, or running a workflow to analyze and update records. Classification is based on the activity actually performed and the existence of a work order, regardless of whether the request was made through an application screen, chat, API, or integration.

Before a metered execution begins, the platform or the contracting instrument will identify the applicable regime: dynamic consumption or a fixed-price unit of work and, where applicable, the Execution Profile. Transitioning from Copilot to Autopilot requires confirmation or prior authorization from the Customer.

This authorization may cover an automation, schedule, integration, or workflow previously configured by an authorized person, without requiring a new confirmation for each occurrence. It must comply with the approved scope, permissions, and limits. An included interaction does not silently initiate a new billing method.

5 Use of Workbench

Opening Workbench, checking status and history, reading or downloading existing results, commenting, assigning responsible parties, and manually approving or rejecting a deliverable do not, by themselves, generate additional AI execution consumption.

Requesting generation, AI review, reprocessing, analysis of new files, or resumption with new tasks may generate additional consumption. An approval that releases the continuation of previously authorized work allows subsequent tasks to be metered. Charges arise from processing, not from the approval click.

The availability of a chat for monitoring work in Workbench does not make executions requested through it part of included Copilot use. Any access licenses and other platform fees remain subject to the Order.

6 Dynamic consumption

Under dynamic consumption, debits reflect the resources actually used by tasks and execution attempts. Conversion into credits follows the applicable rate table and may take into account models, input and output, processing, pages, tools, integrations, and validation or review steps.

Data complexity, volume, and quality, the Execution Profile, and the number of attempts may affect consumption. The same type of request does not guarantee an identical debit across executions. Records may be consolidated during or after processing.

The applicable rate tables must allow the metric and charging rule to be identified, including any factors and rounding rules used. Changes will apply prospectively, subject to conditions expressly fixed in the Order. An estimate is not a spending cap.

7 Fixed price per unit of work

Repetitive work with a known scope may be contracted as a Classified Unit of Work. For each class, the Order or its attachment defines the purpose, input data and documents, inclusion and exclusion criteria, execution workflow, profile, expected deliverables, quality controls, and the milestone at which the unit is counted for billing.

The fixed price may be expressed as a monetary amount per unit, a fixed number of AI Credits, or an allowance of units with an aggregate price and an overage rule. These are forms of settlement under the same fixed-price regime and do not create a third execution regime.

Unless a different milestone is expressly stated in the class definition, each unit is counted when the item reaches the first billable task defined for that unit. In batches, each item is counted separately upon reaching that milestone. Counting a unit does not depend on delivery of the final result.

Ordinary variations in complexity and the attempts covered by the class scope are absorbed into the fixed price. Work included in the unit will not also be charged under dynamic consumption. Excluded resources or activities must be identified in the contractual arrangement.

A new submission, a new work order, a material change in data, or a change in scope may constitute a new unit. Items that fall outside the criteria may be handled under another class or dynamic consumption, pursuant to a previously authorized rule or a new confirmation. There will be no silent conversion from fixed pricing to dynamic consumption.

8 Profiles, estimates, and failures

The Normal, High, and Maximum Execution Profiles retain the work’s objective, functional workflow, and expected deliverables while varying the model configuration and the intensity of checks and reviews. More intensive profiles tend to consume more resources, without a universal multiplier or a guarantee of a better result in each execution.

Profile availability depends on the offering and the organization’s permissions. A workflow may require a minimum profile. For a fixed-price unit, the included profile must be defined; another profile may require a different class or an express commercial condition.

Estimates, simulators, and consumption ranges are informational and depend on the assumptions used. A numerical estimate before every execution is not guaranteed. Under dynamic consumption, measured consumption prevails unless a binding limit or condition has been expressly contracted; under fixed pricing, the price of the applicable unit prevails.

Interruption, cancellation, failure, timeout, or the absence of a final result does not automatically reverse charges for resources already used. Input validation, recovery, retries, and checks may generate consumption. Missing, illegible, or inconsistent data may require additional effort. Under fixed pricing, the treatment of attempts and failures defined for the class applies, without duplicating the price of included work.

A new execution requested by the Customer is metered under the applicable regime. A metering error or a failure acknowledged to be attributable solely to the platform may result in an adjustment or credit, in accordance with the Terms of Use and the applicable remedy. Looplex will review the records of the affected execution; cancellation or dissatisfaction with the result alone does not constitute a billing error.

9 Availability, replenishment, and validity

The Order specifies the number of credits, the contracted commitment, the consumption cycle, and replenishment and expiration dates. The first cycle of the included allowance follows the subscription start through actual or deemed activation, unless expressly provided otherwise. The following general rules apply:

Commitment	Availability and validity
Monthly	Credits are made available in full at the beginning of each monthly cycle and remain valid until the end of that cycle.
Annual	Credits are made available in full at the beginning of the contract year and remain valid until the end of that year.
Multiyear	An annual allocation is made available at the beginning of each contract year. Each balance expires at the end of the corresponding year, with no rollover to the following year.

Payment in installments does not change the consumption cycle. An annual allowance may be used predominantly in certain months, without mandatory monthly releases. Under a 24-month contract, first-year AI Credits do not automatically remain valid through the end of the second year.

Unused credits expire at the end of their validity period, without rollover, conversion into cash, transfer, or refund, except as expressly provided, pursuant to an acknowledged adjustment, or as required by law. Unit-of-work allowances follow the quantity and period defined for the class.

10 Additional packages and consolidated balance

Nonrecurring or recurring additional packages are made available upon purchase, unless expressly provided otherwise. The usable balance is the sum of unexpired credits under the commitment and additional credits. There is no contractual order of priority for consuming credits from these sources; the platform may maintain separate lots with their own dates to track expiration.

A nonrecurring add-on has its own validity period, equivalent to the applicable consumption cycle, starting when it is made available: one month for a monthly cycle or one year for an annual cycle, including under a multiyear contract, unless the Order provides otherwise. Replenishment of the main allowance does not shorten or restart that validity period.

For example, in a monthly cycle starting on the 5th, a nonrecurring add-on made available on the 12th will generally remain valid through the 11th of the following month, even if the main allowance is replenished on the 5th.

A recurring add-on has an initial transitional allocation that remains valid until the end of the current main cycle. From the next replenishment onward, it is made available and expires together with the main allowance. The Order must specify the price and quantity of this initial allocation, including any proration; proration is not presumed.

In the same example, the initial recurring allocation made available on the 12th expires on the following 4th, and both allowances are replenished on the 5th. For annual or multiyear plans, alignment occurs on the anniversary of the annual cycle.

11 Limits and overage consumption

The Order or the authorized configuration will specify how an insufficient balance is handled: blocking new executions, an additional purchase, replenishment, or overage consumption at the agreed rate. Continued use with additional charges requires authorization, which may be granted in advance for defined workflows or limits.

Alerts, budgets, and soft limits do not guarantee an automatic stop. A limit expressly identified as a hard limit blocks new metered executions but may not interrupt tasks already in progress or prevent consumption that has already occurred from being recorded later.

Available controls depend on the offering and may be applied by user, team, product, integration, workflow, profile, or work class. The Order must identify which controls are enabled and who may authorize overages. These controls do not create additional pricing methods.

12 APIs, integrations, and third-party resources

The access channel does not change the nature of the operation. A Copilot call is subject to access rights and fair use; an Autopilot work order is metered under dynamic consumption or the contracted unit.

Querying existing data, metadata, status, or results without new Looplex AI processing does not incur AI Credit charges for inference that was not performed. Expressly contracted platform, data, API, or integration fees may apply.

When the Customer’s external model performs inference in the Customer’s own account, the cost of that model is not included in Looplex AI Credits. If the integration also initiates an Autopilot execution, that execution will be metered normally. Programmatic use of Copilot at scale may require separate access rights and fees.

13 Projects, records, and termination

AI consumption during Professional Services is governed by this policy unless expressly included in the project price. The Order or SOW must define the included resources, their limits, and the treatment of overages, avoiding duplicate charges.

The Customer may view or request available balance, validity, and consumption records for verification. Their presentation and level of detail in the product depend on the contracted features. Records may reflect processing or consolidation that occurs after the request.

Disputes must identify the affected charge or execution and be submitted within 30 days of the invoice or the record being made available, except in cases of manifest error. Acknowledged errors will be corrected in the corresponding balance or billing.

Plan changes and termination will be governed by the Order and the Terms of Use. They do not create an automatic refund, transfer, or extension of credits and do not eliminate consumption already incurred or commitments undertaken. A remaining balance, including an add-on with its own validity period, does not extend access rights that have ended.

This policy addresses consumption and billing. Use of results, professional review, data, licensing, and liability remain subject to the other contractual documents. Updates to this policy will apply prospectively and will respect the conditions expressly fixed for the contracted period.