Chat settings
Every Chat setting, in one map. Settings opens from the avatar menu, with a grouped sidebar: Account, Usage, Appearance, AI, Privacy & data, and About — plus Admin where you have console access.
General settings
| General | What it covers |
|---|---|
| Profile | Avatar, full name, username, interests, password set or reset, email change, SSO link or unlink, and revoking external authorizations. The full name field shows the name saved on your account, so you can correct or clear one you never chose, such as a string made from a random sign-up address. |
| Credits | First in the Usage section of the sidebar. Axelera Mercury 1.0 does not draw on your credits on any plan. It carries a fair-use ceiling, set high enough that ordinary use never meets it and low enough that an unattended script cannot run the free tier flat; the ceilings reset at 00:00 UTC, they are an operator setting rather than something a plan grants, and the same ones apply whether you are on the free plan or an enterprise one. Reach one, or ask for Mercury while it is briefly busy or paused for maintenance, and Chat says which of those happened and asks you to try again rather than charging you or quietly answering from a tier that costs credits. If your own requests still running have reserved every credit that is left, or your seat has reached a monthly cap, a new request runs on Axelera Mercury 1.0, which draws on no credits, instead of waiting or stopping, and Chat says so in the line above the message box. Several requests can run at once on any plan. Axelera Venus 1.0 and Axelera Earth 1.0 draw on credits. Your credit balance for the current period: the spendable balance up top (credits reserved by requests still finishing are already subtracted), the tier you used most this period with its task count, each credit grant in the order grants are spent, soonest to expire first, with its expiry date or, for the welcome credits, no expiry at all, a balance-over-time chart for the period, and daily usage split between premium and everyday answers. Where a grant arrived after an overdraft, the part of it that went to repaying that overdraft is shown on its own line, so a bucket that opens below what it was granted with never reads as usage you did not have. Your grants and what each one is valid until show on this page; it is the one place that lists every grant, what is left in it, and the date it expires or that it never does. If a monthly cap has been set for your seat, the page also shows that cap and what you have used against it this month. The cap resets at the start of each month, and Axelera can raise it before then if you ask. Seats without a cap see no cap section at all. A run that is one turn from finishing may overdraw a small amount once a day, and the next credits you receive repay it. When you ask for an upgrade, Axelera's sales contacts receive one email with the amount you asked for and whether it is for you or your team, and they reply to the email address on your account. |
| Usage | Your activity, opening with headline totals: overview figures, heatmap, model and assistant rankings, credits burned per UTC day split between premium and everyday answers (a month with no burn, or an account that is not metered, shows a sentence in place of that chart), a line-item request table, a shareable summary image, and the team leaderboard where teams are enabled. Everything on this page is counted in credits, never tokens and never currency, and the month picker moves every section below it. Your balance, your grants and what each one is valid until live on the Credits page instead. Compact notes identify partial history, unpriced direct-provider calls, or usage still being reconciled without presenting those conditions as running out of credits. If one request needs more credits than you have left, shorten it or select a direct provider configured with your own API key. |
| Interface | Theme mode, primary and neutral colors with live preview, and font size. Theme sits at the end of the page, after the choices you set once. |
| Chat | Chat display: streaming auto-scroll, code highlighter theme, and Mermaid theme. |
| Language | Interface language and the language agents reply in. |
| Notifications | The notification inbox with mark-read, mark-all-read, and archive actions. |
The app opens in dark by default. Light stays fully supported and one click away, and choosing either keeps it. Theme and language also do not require the settings page: quick switchers live in the user panel, the home footer, and the mobile Me header. Settings are for the durable choice; the quick menus are for right now. Google Sans Flex is included with the app, so you do not need to install it or connect to Google Fonts. Code stays monospace, and characters outside the bundled font use your system fallback.
Agent settings
| Agent | What it covers |
|---|---|
| Provider | Axelera Auto uses company-managed model credentials and applies one quota contract across its configured managed providers. Admission uses a provider-neutral local bound, then the selected provider's final usage is reconciled to the exact charge. Changing which managed model answers does not create a separate quota path. Selecting OpenAI, Anthropic, Google Gemini, Moonshot, or another provider directly requires your own API key or OAuth connection; company credentials are never reused for a direct selection. |
| Model | Per-provider model lists: fetch remote models, add custom ones, and set context windows, deployments, and capabilities such as tools, vision, and reasoning. |
| Service Model | The background models behind the product: topic naming, translation, history compression, prompt and query rewrite, input completion, speech-to-text, and text-to-speech. |
| Memory | The memory enable switch and the low / medium / high effort slider — detailed on the Memory page. |
| API Key Management | Create named keys with expiry; the table shows status, last used, and per-key show, copy, edit, disable, and delete. |
Connecting a model provider
System settings
| System | What it covers |
|---|---|
| Privacy | One home for what is collected: the analytics-cookie choice and the telemetry switch, both changeable at any time, plus a chat review choice on accounts that offer one. |
| Your data | Knowledge-base usage, import and export of your own data, and how to request account deletion. |
| Reset | Clearing stored data and resetting settings to their defaults. |
| About | App version, build channel, server version, update checks, the official site, support email, the email for privacy rights requests, terms, privacy, and telemetry links. |
| Proxy (desktop only) | Route traffic through HTTP, HTTPS, or SOCKS5 with host, port, authentication, and a test URL before saving. |
| System tools (desktop only) | Detection of local runtimes, content, file search, and browser automation tools — availability, version, path, and re-detect. |
Plans and credits
| Plan | Price | Seats | Monthly credits |
|---|---|---|---|
| Launchpad | Free | 1 | 300 |
| Pro | EUR 20 a month, EUR 17 billed annually | 1 | 2,000 |
| Ultra | EUR 200 a month, EUR 167 billed annually | 1 | 20,000 |
| Team | EUR 60 per seat a month, EUR 50 billed annually | 2 to 24 | 6,000 per seat, pooled across the account |
| Enterprise | From EUR 120 per seat a month | 25 and up | 12,000 per seat, pooled across the account |
What credits pay for
Axelera Mercury 1.0 chat is unlimited on every plan, the free one included, and never draws on credits. Credits pay for Axelera Venus 1.0 and Axelera Earth 1.0, and for the work an agent does on your behalf. As a rule of thumb a Venus question costs about 3 credits and an Earth question about 12; a full pipeline built end to end costs about 200 credits on Venus and about 220 on Earth.
How your account gets a plan
Launchpad is the plan your account is on from the moment it exists, and its 300 monthly credits arrive on their own each month: nothing to choose, nothing to claim. Pro, Ultra, Team and Enterprise are arranged with Axelera and recorded against your account after purchase, and the plan starts granting its credits from the day Axelera records it. A Team and Enterprise purchase also opens the shared pool your seats draw on and puts each seat in it, so everyone bills to the same balance. Axelera records how many seats your company bought, and the pool is granted that many seats of credits each month, or one seat's worth for every person in it when that is more, so credits for a seat you paid for arrive before the person who will use it has joined. Seats added during a month bring their credits straight away; a lower seat count applies from the next month, and the credits already granted this month stay.
Shared plans: one balance for the team
On a Team and Enterprise plan your seats share one balance rather than each holding their own, so a month that is quiet for one person leaves more for everyone else. The Credits page shows that shared balance, what the team has spent so far this period and when it resets; it never shows you what any individual colleague spent.
Your company can have its own administrators for the team, named by Axelera when the team is set up and by each other after that. They run the team from Settings, Team: they invite colleagues by email, set monthly caps, suspend or remove a seat and name other administrators. They see how many credits each person on the team used in a month, each person's cap and whether a seat is active. They never see anyone's conversations, files or questions. Removing a seat, inviting an administrator and changing who is an administrator each need a code emailed to the administrator making the change, and every administrator gets an email when someone becomes or stops being one. An invite arrives by email: sign in with the invited address and accept it from the banner on the home page or the Credits page. An invite stays open for 14 days, and an address outside your company's recorded email domains is only invited after an administrator confirms it.
A monthly credit cap is set for a seat by your team's administrators, or by Axelera on request, either the same cap for every seat or a different one for a particular seat. A cap bounds what one seat may draw from the shared balance in a month; it is not a separate allowance, and leaving it unset is normal. If you reach your cap, your requests continue on Axelera Mercury 1.0, which draws on no credits, and Chat says so in the line above the message box, with the day the cap resets. A seat cap and a team that is out of credits are different problems with different answers: the cap resets at the start of the next month, and your administrators can raise it before then if you ask. Settings, then Credits, shows your own cap and what you have used against it; the per-seat figures for the whole team are on your administrators' Team page.
Your first credits, and topping up
When credits run low, and when they run out
Chat tells you before it matters, in a line above the message box. While credits are still there but running low, it says how many are left and when they reset. When you have picked Axelera Venus 1.0 or Axelera Earth 1.0 and a request cannot be paid for from your credits, your work does not stop: the line reads Keep working with Axelera Mercury 1.0, new requests run on Mercury, the everyday tier that is free on every plan, and the answer that first moved says so. The line also says why and when your chosen tier comes back: this period's credits are used up and return when your plan renews, your seat has reached its monthly cap until the start of next month, your requests still running are holding the credits that are left, or a conversation has grown longer than the credits left can cover, while shorter turns, in a new chat for example, stay on your pick. Your pick stays as it is, so Chat goes back to it by itself. Only when Mercury has also reached its own daily fair-use limit does anything actually stop, and the line then says when that limit lifts. Each of those lines carries a Request upgrade button. It opens a short form: choose one of the top-up blocks or another amount in whole thousands, up to one million, then say whether the credits are for you alone or for your team, and how many people that is. There is no free-text field and no self-serve checkout yet, so sending it records your request and an Axelera contact follows up. The same form is on its own page at /upgrade.
Moving from the old monthly quota
Credits are the only balance Axelera Wingman keeps for you: one number, spent by Axelera Venus 1.0, Axelera Earth 1.0 and agent work, topped up by your plan each month. Accounts that existed before credits became the balance also receive 3,000 credits a month for 3 months, on top of the one-off gift above, so nothing changes for you while a plan is arranged. Nothing you use is priced to you in currency, and no page shows you a bill in dollars. The Axelera team sees your account the same way, in credits: your plan, what you have left, what you have used this month and when your plan's credits renew. Credits they grant you, or a plan they put you on, show on your Credits page the next time you open it.