Console: licences, usage and billing
For the administrators of your AlphaAgent Console organisation, the separate site holding your licence keys, AWS Marketplace subscription and Organisation credential. Licence keys need a licence operator or administrator permission; revoking a key and managing the Organisation credential need the administrator permission.
Before you start: the dock has Billing (Subscription, Reported usage, Statements), License Keys (All Keys), Organisation and Organization & profile. A licence key needs an active AWS Marketplace agreement linked to your organisation (Console account, offer and licence).
Create a licence key
- Open License Keys. One licence authorises one Studio deployment; revocation is irreversible.
- Click New license key. When your organisation may not create one, the button is disabled and a badge names the reason: no linked Marketplace subscription (open Billing → Subscription), the Marketplace integration not configured, billing state unreadable, or a subscription no longer active.
- Enter a Name (required) and optional Description, then click Create license key.
- On the key's page, Reveal token and Copy token read the masked License Token. This whole value, which contains a dot, is what the deployment wizard's Licence step asks for (Deploy your first Studio).
Read and revoke a licence key
The list searches by licence id or name and filters by status; columns are License ID, Name, Deployment (Not deployed until a Studio activates with it, then Deployed; Revoked after revocation), Heartbeat (with "(N missed)"), Last seen and Status.
A key's page shows Name, License ID (masked; Reveal ID), Status, Heartbeat and Last seen, with Save and Revoke, then Basic information (editable Name, Description); License key (License ID, License Token, Activated at; "Unavailable" once revoked); Heartbeats (Period start, Period end, Status, Version reported, Received); and Consumption, a chart by Period (Last 24h, Last 7 days, Month to date, Last 30 days), Granularity (Hourly, Daily) and Split (By model, By activity) with Billing period, Prompt tokens and the estimated cost, per rate when more than one applied.
Revoke stops future usage immediately; usage already incurred is still billed; the secret is destroyed and cannot be reissued, so you create a new key to redeploy.
Read Billing
Subscription is headed AWS Marketplace subscription: prompt-token usage from every deployment licensed under this account is reported to AWS hourly and appears on your AWS bill as "AlphaAgent: Prompt tokens". The strip shows Status (Active, Not linked, Linked, no active agreement, or Suspended), AWS account (the buyer), Rate (per million prompt tokens), Month-to-date tokens, Reported to AWS, Est. charges (MTD) and License keys (Can create, or why not). Open AWS Billing opens the buyer account's console; an unlinked organisation sees Subscribe on AWS Marketplace, or that your private offer link is sent by PrometheusRL.
Usage by license key lists each key's prompt tokens this month and share, then Total, reported to AWS Marketplace, Reported to AWS so far (Marketplace cursor) and Accrued since the last hourly report. The rule: calendar month, UTC, every key on the account; tokens count in the hour their turn finished; each hourly run reports what accrued since the previous run, stamped to the previous hour; days before the agreement's effective date and evaluation days are excluded.
Agreements lists Agreement, Status ("active · metering" or "deprovisioned"), Started, Ended, Rate and License. Usage is metered against the most recently started active agreement, so after accepting a private offer cancel the superseded public subscription. A new agreement appears within a few minutes.
Reported usage is one row per hourly report, by month: Reporting hour, Status, Prompt tokens, Units metered, Late (prior month), License and AWS record (the receipt on your AWS bill), with Period, Tokens reported, Units metered, Reports and Attention (pending or rejected) above.
Statements is one row per calendar month, produced shortly after it closes: Period, Prompt tokens, Units metered, Late (prior month), Est. amount and Licenses, with Statements, Tokens (all time) and Est. charges (all time) above. Amounts are estimates at your agreement rate; AWS issues the invoice in your AWS Billing console.
Read Organisation
Organisation credential is the token your Organisations installer authenticates with, shown once at creation and at each rotation. With none, an administrator sees Generate credential; with one, ID, Created, Last used and Status, plus Rotate (a new credential now, the old one invalid immediately; your Organisation stops working until you run the installer's console-credential step with the new value, see Upgrading Organisations) and Revoke (type the id; the secret is destroyed permanently).
Organisation bundle lists every Organisations release with Version (newest marked latest), Notes, Released and Download; only the latest offers Download bundle, older rows read Superseded.
Read Organization & profile
Your First name, Last name, Job title and Phone number with country code; under Business, Organization name, Industry, Company size and Country (billing); under Billing address, Address line 1, Address line 2, City, State / Region and Postal / ZIP code. Click Save changes. There is no Members screen yet; for access to your Console organisation, see Support.
What you should see
Three separate things describe a key.
Status is the lifecycle: active, inactive or revoked. Studio on an inactive key stops with "This license is not active. Contact your administrator to restore access." and recovers on its next check once the key is active again. Revoked is final: "This license has been revoked. Contact your administrator."
Heartbeat is connectivity, for display only: pending until the first beat, healthy while beats arrive every five minutes, warning after one or two missed periods, unhealthy after three or more. A missed beat does not stop Studio.
Enforcement is a hold placed by AlphaAgent operations; each carries the message Studio users see:
| Hold | Studio | Message shown in Studio |
|---|---|---|
| Payment overdue warning | Keeps running; amber Billing alert: banner | "A payment on your account is overdue. Please settle it to avoid your AlphaAgent deployment being suspended." |
| Billing suspended | Stopped | "AlphaAgent has been suspended due to an unresolved billing issue. Contact your administrator to restore access." |
| Suspended by administrator | Stopped | "AlphaAgent has been suspended by your administrator. Contact your administrator to restore access." |
| Terms violation | Stopped | "AlphaAgent has been suspended pending review of an acceptable-use issue. Contact your administrator." |
| Security hold | Stopped | "AlphaAgent has been suspended as a security precaution. Contact your administrator immediately." |
| Trial expired | Stopped | "Your AlphaAgent trial has ended. Contact your administrator to continue." |
| Decommissioned | Stopped | "This AlphaAgent deployment has been decommissioned. Contact your administrator." |
| Maintenance | Stopped (a warning only if AlphaAgent configures it so) | "AlphaAgent is temporarily unavailable for scheduled maintenance. Please try again shortly." |
The two billing holds also banner the Console's licence and billing pages as Payment overdue: (settle the AWS Marketplace invoice in your AWS Billing console) or Billing suspended: (no active agreement; re-subscribe and link it), each with Manage billing.
Notes
- Studio checks its licence with the Console every five minutes. When a check fails (Console unreachable, or a response failing its security checks) Studio stops serving every product request and shows Service halted ("AlphaAgent cannot reach the AlphaAgent Console and has been disabled. Contact your administrator."), retrying every 30 seconds until a good check. A tampered response is treated as permanent until the deployment restarts. See Banners you may see.
- Billing counts prompt tokens (the input side of every model call) from billable activity: coordinator turns, worker nodes, the Governor, context and thought-map summaries, visualisation contracts, coder analysis, workflow conditions, PII redaction, knowledge-graph builds, edge discovery, embeddings and retrieval, connector guides and connector credential inference. Completion and cache tokens appear as counters in the Organisations console's exports but are not billed; stream metadata is never billed. Every Console figure is an estimate; the AWS bill is authoritative.
- To change your rate, accept a new private offer from the same buyer account, then cancel the superseded subscription.
- If the buyer account's subscription ends, keys cannot be created and the licences fall under the billing-suspended hold; re-subscribing from the same buyer account and linking it recovers automatically.
- One Console organisation, one buyer AWS account, and the reverse. A licence key has a name and a description only: no plan, seat count or expiry.
- Enforcement holds are placed and lifted by AlphaAgent operations.
- A key reading unhealthy while Studio works means beats are not reaching the Console; check the deployment's network path.