> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Credits and billing

> Fund your workspace, manage automatic top-ups, and understand how usage consumes credits.

## Monthly minimum, paid annually

Your minimum monthly commitment is based on estimated monthly volume and starts at **CAD 1,000.00**. You pay **12 times that amount at signing and every 12 months at renewal**. At the minimum, the payment is **CAD 12,000.00**.

There is no scheduled monthly payment. Monthly usage is deducted from the prepaid balance. Additional top-ups fund usage when needed and do not start a new agreement term.

## One workspace credit balance

Your workspace shares one balance across AMLOK Insights and AMLOK Signal. Paid and promotional top-ups both become unused credits in that balance, with no consumption priority.

* **Insights:** a completed full underwriting consumes credits at the assigned tier and agreed rate.
* **Signal:** each active borrower or business is charged once per workspace per month at the start of the month, with a full charge immediately on first activation during a month. Monitoring and change-driven reassessment are included, without an additional Insights charge.
* **Unused credits:** remain available while your account is active.
* **Used credits:** are non-refundable.

Available credits are the balance you can spend. Spent credits are the amount already deducted for products, less correcting reversals. There are no reserved amounts or separate credit buckets. Successful top-ups increase available credits; a service charge reduces them and increases spent credits. Payment attempts still in progress remain payment history until successful.

## Additional credits and automatic top-ups

In the **client portal**, you can add or change a **card or bank account**, enable or disable automatic payments, and configure the top-up threshold and amount.

| Setting | Policy |
| - | - |
| Automatic top-up trigger | CAD 200.00 by default; you can select a higher threshold |
| Minimum automatic top-up amount | CAD 500.00; the amount charged is the amount you selected |
| Payment methods | Card or bank account |
| When auto-pay is enabled | Available credits below your threshold trigger collection from your selected payment method |
| When auto-pay is disabled | No automatic collection occurs; you can add credits through the portal |

**CAD 200.00 is a trigger, not a balance floor.** Requests can continue below it while available credits cover their cost. For example, a CAD 35.00 charge can reduce CAD 215.00 to CAD 180.00. With auto-pay enabled at the default threshold, that balance triggers your selected top-up.

A pending or failed payment is not spendable. If credits cannot cover the next billable operation, AMLOK rejects it with an insufficient-credits error and does not charge for unprocessed work. Retry after funding is available. Read-only reports remain accessible while your account is active.

A higher threshold and a suitable top-up amount help avoid interruptions, but processing still depends on available credits and successful payment.

## Renewal and rollover

At each 12-month review, AMLOK reviews actual usage, expected growth, workload complexity, and applicable volume discounts. The next monthly minimum and rates are agreed for renewal, and the payment for the next 12 months is due at renewal.

Unused credits carry forward while the account remains active. Your agreement specifies how any carried balance is treated when calculating the renewal payment.

## Rates and rounding

Prices and credit amounts use CAD with **two decimal places**. The effective unit rate is rounded to two decimals first, then multiplied by the billable quantity. Each charge is rounded to two decimals using decimal half-up rounding. Totals sum the rounded charge amounts.

Negotiated pricing uses Standard, Advanced, or Complex with an agreed rate and workload limits. It does not introduce a fourth tier.

## Cancellation and unused credits

When cancellation is submitted in the portal or set by your account manager, all product processing, usage deductions, and new or scheduled top-ups stop immediately. Pending processing is cancelled without another charge.

You can request cancellation at any time in the portal, without a notice period. Enterprise clients can also use their dedicated account manager. Full account closure takes place at the end of the request month.

AMLOK issues an immediate refund of **the entire unused balance**, including promotional credits, at account closure. A saved bank account in the portal is required, even if you funded by card. Bank delivery can take **7-10 business days after issuance**.

Workspace data is deleted after the request month closes and the necessary final information is generated. See [cancellation and refunds](https://docs.amlok.io/pricing/refunds-and-payouts.md) for the sequence.

## Processing and completion

An Insights request checks available credits before acceptance and deducts once when the agreed output is successfully completed and published. Acceptance does not reserve or spend credits. Concurrent completions cannot spend the same credits: the balance check, charge and publication are atomic. If another operation uses the balance before completion, that underwriting waits for funding without publishing its final output or creating a duplicate charge.

Signal deducts before monthly monitoring proceeds. Verification, searches, calculations and investigations are included product stages with no separate AMLOK charge. See [product scope](https://docs.amlok.io/api-reference/products-and-endpoints.md).

## Reporting access

Use [consumption reporting](https://docs.amlok.io/api-reference/consumption-reporting.md) and [credit reporting](https://docs.amlok.io/api-reference/credit-reporting.md) to reconcile usage, balances, and statements. Each API key belongs to one workspace. Payment settings, top-ups, and cancellation are managed in the portal, not through public API commands.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.