Billing

Hal is billed per identity, with an invoice generated on the first of each month for that month and charged to a card or US bank account saved with Stripe. The rate, the minimum and what counts as an identity are on the pricing page. This page is what billing looks like from your portal and your inbox. Hal’s AI usage is a separate bill, from Anthropic to your own account: Controlling AI spend.

Settings → Billing

Settings → Billing is where an administrator sees and manages billing:

• The payment method. Green with the card or bank account on file; red with what needs doing, when none is on file or the last charge failed, in Stripe’s own words.
• The status line. When your evaluation ends and billing begins, and at what rate; once you are paying, the rate and how you are invoiced; after notice to end the service, the date it ends.
• Manage payment method and invoices, which opens Stripe’s billing page: replace the card or bank account there and see your invoices. Card and bank details are entered with Stripe and never pass through HAL AI’s systems.
• The identity counts. Today’s billable identities, this month’s high-water mark, the previous month’s peak, and a table per client and tenant. Hal counts once a day.

How each invoice is worked out

The invoice is generated on the first of each month for that month, at the previous month’s peak: the highest daily identity count recorded in the month before, which is already on Settings → Billing when the invoice arrives. The invoice is charged to your payment method when it is issued, and Stripe emails the invoice and its receipt to your billing contact.

When the evaluation ends

Nothing is charged during the 14-day evaluation. Through its final week Hal reminds you when billing begins: an EVALUATION line in the daily digest, a banner on the dashboard and the Health page, the status line on Settings → Billing, and an email to the owner on your account, with your billing contact copied. Each gives the rate, what the first invoice covers, and today’s identity count.

The first invoice is issued and charged the day after the evaluation ends, for the rest of that month, prorated by day. If no valid payment method is on file then, Hal pauses until that invoice is paid. To end the evaluation instead, tell us before it ends, and nothing is charged.

When a payment does not go through

When a monthly charge fails, or no payment method is on file when an invoice is issued, Hal warns you each day until the invoice is paid or he pauses. The red badge on Settings → Billing and a banner on the dashboard say what is owed (the invoice and its amount, or the total when more than one is unpaid), why it did not go through, the day Hal pauses and how many days are left, and the owner on your account gets the same notice by email each day.

On Settings → Billing the button reads Update payment method and opens Stripe’s page for it. When you return, the payment is tried at once, and once it goes through the warning clears within a minute. Stripe also retries the invoice on its own.

If it is still unpaid, Hal pauses at the start of the fifth day after the invoice date, in your portal’s time zone. The evaluation’s first invoice has no such grace: its warning is the final-week reminder, so if it cannot be collected, Hal pauses at once.

While Hal is paused

The owner on your account gets one email when the pause begins. Then:

• The portal opens the pause page on every visit, naming what is unpaid. An administrator who signs in is taken straight to Stripe’s page to add a payment method. The payment is tried when they return, and Hal is back within a minute of it going through. Anyone else sees the notice only.
• Chat, in the portal and in Slack, answers with the same notice and does no analysis. What you asked is kept, so Hal has it when he resumes.
• Stopped: collection from Microsoft 365, Google Workspace and the other services Hal reads through their APIs, and triage, investigations, Sentry, watches, Zendesk ticket review, the night shift and the daily digest.
• Still running: logs your Windows endpoints and network devices send keep arriving and are stored, and the collector keeps installing and updating. The daily identity count keeps running, and billing continues through the pause.

When the pause lifts, Hal picks up each source where he left off, as far back as its vendor still holds events: Recovery windows gives each source’s limit, so a long pause can lose events from the sources with the shortest windows. The pause stays on record on the Maintenance page and in the next digest.

Ending the service

After the evaluation, service is month to month, and the notice period is on the pricing page. Once your notice is recorded, the status line and the dashboard banner give the date service ends, the daily digest carries a SERVICE ENDS line, and the final invoice covers through that date.