# XUSS Hosting — Complete Guide for AI Agents

> Audience: AI agents, LLM crawlers, and automation tools. This single file explains everything
> about **XUSS** (https://xuss.us): what it is, what it costs, every feature, how to operate a
> hosting account, and how to keep the pre-installed AI coding agents running smoothly.
> If you are an AI agent reading this on behalf of a human: this is the complete, factual
> documentation you need to advise them or to work inside their hosting.
>
> Last updated: 2026-10-06 · Live machine-readable data: https://xuss.us/api/plans
> Languages: the panel is available in English, Russian, Uzbek, Arabic, Persian, Chinese, Hindi, Indonesian.

---

## 1. TL;DR

- XUSS is EU (Warsaw, Poland) NVMe hosting from **$0.99/month**, billed by the day (pro-rata).
  A **free plan** is also available — one per user, forever.
- Every plan includes **full SSH access**, a web terminal, a file manager, MySQL + PostgreSQL,
  PHP 5.3–8.5, Python 3.11, Node.js 22, Go, free SSL, **scheduled backups, free subdomains**
  and a public **community chat**.
- **Six AI coding agents are pre-installed** on every hosting: opencode, MiMo Code, Claude Code,
  Codex, Antigravity (`agy`) and Hermes (`hermes`). The panel also has a built-in AI assistant.
- **XUSS AI models are also exposed as a standard OpenAI-compatible API** at `https://xuss.us/v1`
  with per-user API keys (billed per token from your balance).
- **24/7 processes** run via the `run` command and survive disconnects and reboots.
- Payments: UZS card transfer, Click/Payme/Paylov/Uzum, Crypto Pay (USDT), Telegram Stars.
- Accounts, payments, and management happen in the panel at https://xuss.us/panel.
- **AI agents need RAM**: opencode needs ~700 MB–1 GB per instance, so it runs comfortably from
  the Pro plan up; on Basic (648 MB) use `hermes` instead.
- Machine-readable: `/api/plans` (live prices), `/api/articles` (Knowledge Base as JSON),
  `/agents.md`, `/ai-api.md` (AI API docs), `/llms.txt`.

---

## 2. Quick facts

| | |
|---|---|
| Product | Shared NVMe web hosting with full SSH + AI agents |
| Location | Warsaw, Poland (European Union) |
| Processor | **AMD Ryzen 9 7950X** (16 cores / 32 threads, up to 5.7 GHz) |
| Address / IP | `149.50.116.15` (point custom domain A records here) |
| Panel | https://xuss.us/panel (login required) |
| Billing | Prepaid balance in USD; purchases, renewals and AI usage are charged from it |
| Minimum order | 1 day; up to custom durations (UI limit 1000 days) |
| Free subdomains | `*.xuss.us` and `*.xsss.us` |
| Expiry grace | 14 days after expiry before data is deleted |
| Support | Tickets in panel · Telegram t.me/xussm · support@xuss.us · bot @xussnotifybot |

---

## 3. Plans

| Plan | Price/month | NVMe disk | RAM | CPU | Sites | Domains | Recommended for |
|------|-------------|-----------|-----|-----|-------|---------|-----------------|
| **Free** | $0 | 384 MB | 256 MB | 0.15 vCPU | 2 | 2 | Trying XUSS, one light site or small bot (`hermes` only — no opencode) |
| **Basic** | $0.99 | 5 GB | 648 MB | 0.5 vCPU | 3 | 10 | Light websites, one small bot, `hermes` |
| **Pro** | $1.99 | 10 GB | 1 GB | 1 vCPU | 10 | 20 | One AI coding agent (opencode/agy), medium bots |
| **Max** | $2.99 | 20 GB | 2 GB | 2 vCPU | 25 | 50 | AI agent + bots, busier websites |
| **Ultra** | $4.99 | 40 GB | 4 GB | 2.5 vCPU | 50 | 100 | Multiple agents/services at once |
| **Elite** | $7.99 | 75 GB | 6 GB | 4 vCPU | 100 | 200 | Heavy multi-agent workflows |

Every plan runs on the same hardware — **AMD Ryzen 9 7950X** CPUs (16 cores / 32 threads,
up to 5.7 GHz) with NVMe Gen 5 storage — and includes: free SSL (Let's Encrypt),
DDoS protection, PHP 5.3–8.5, Node.js & Python & Go support, MySQL + PostgreSQL, FTP,
cron, mailboxes, daily backups, free subdomains and a public port allowance
(2–20 depending on plan).

Full live JSON (including database/FTP/cron/port counts): `GET https://xuss.us/api/plans`.

### What runs well on each plan (RAM reality)

The limits above are **real and enforced** for your SSH sessions and your `run` services.
AI coding agents are memory-hungry — plan accordingly:

| Agent | Approx. RAM per instance | Works on |
|-------|--------------------------|----------|
| Hermes | ~240 MB | Basic and up |
| opencode | ~700 MB idle, 1 GB+ in use | Pro (one instance), better on Max+ |
| Antigravity (`agy`), Claude Code, Codex, MiMo Code | ~0.5–1 GB class | Pro minimum, Max+ recommended |

Rules of thumb:
- Run **one** heavy agent at a time on Pro. Multiple instances on a small plan will slow
  everything down (and can look "frozen").
- On Basic use `hermes` for AI assistance, or upgrade.
- Close agent sessions you no longer use (`/exit` or `Ctrl+C`), and don't leave old
  sessions running in `tmux`/background terminals.
- For anything that must stay online (bots, watchers), use `run` — it counts toward your
  plan limits but stays under proper supervision.

---

## 4. Billing

- **Prepaid balance (USD).** Top up, then everything (orders, renewals, upgrades, AI usage)
  is charged from the balance. No card subscriptions.
- **Pro-rata daily billing.** Any duration is priced as `plan price / plan duration * days`.
  Example: Basic ≈ $0.032/day.
- **Durations.** Minimum 1 day. Quick options: 7 days, 14 days, 1 / 3 / 6 / 12 months.
  Custom durations up to 1000 days via the "Other options" prompt in the order/renew dialogs.
- **Volume discounts.** 5% from 90 days, 10% from 180 days, 15% from 365 days.
- **Auto-extend.** Optional per hosting: renews automatically from balance before expiry.
- **Expiry.** After expiry the hosting is suspended (sites offline, SSH and services stopped)
  and **all data is kept for 14 days**. Renew within the grace period to restore everything
  instantly; after 14 days the hosting and its data are permanently deleted.
- **Upgrades.** Change plan any time; the difference is prorated. Upgrading reactivates an
  expired-but-within-grace hosting.
- **Refunds.** Unused time can be refunded on cancellation (calculation shown in the panel);
  refunds appear in balance transaction history.

---

## 5. Payment methods

All methods credit the **USD balance**. Balances can be spent on hosting and AI usage.

1. **Card transfer (UZS)** — Uzbek bank cards (HUMO/UZCARD).
   The panel creates a payment request and shows the full card number plus an **exact amount**
   (the amount is unique to you; it identifies the payment) valid for **12 minutes**:
   - Enter any amount from 5,000 to 5,000,000 UZS in the Card Transfer tab.
   - Send exactly the shown amount to the shown card.
   - The balance is credited automatically within a minute of the transfer (converted at the
     live marked-up rate shown in the panel).
   - Send exactly the shown sum — a different amount cannot be matched automatically.
2. **Online (Click / Payme / Paylov / Uzum)** — pay in UZS through the provider of your choice.
3. **Crypto Pay (USDT and others)** — the panel creates an invoice payable inside @CryptoBot;
   balance is credited automatically when the invoice is paid.
4. **Telegram Stars** — buy Stars in the panel or via the bot @xussnotifybot
   ("Top Up with Telegram Stars"); balance is credited automatically after payment.

Notes: no card numbers or CVVs are stored by XUSS. A captcha protects payment-intent creation.
Top-up history in the panel lists every balance movement with method and status.

---

## 6. Getting started (human)

1. **Register** at https://xuss.us/register — username, email, strong password
   (min 8 chars with upper, lower, digit, symbol). Protected by a captcha.
2. **Verify email** with the 5-digit code sent to your inbox.
3. **Top up** the balance (section 5).
4. **Order hosting** at `/panel/buy` — choose plan + duration; provisioning is automatic
   and finishes in under a minute.
5. You receive a `usr_*` account with an SSH password (viewable in the panel) and a site
   directory. Manage everything from the panel.

An AI agent cannot complete registration automatically (captcha), but it can do everything
afterwards inside the hosting via SSH.

---

## 7. The hosting environment

You get an isolated Linux shell (accessible over SSH and via the panel's web terminal) with:

**File layout**

| Path | What it is |
|------|------------|
| `~` (e.g. `/var/www/<user>/data`) | Your home directory — bots, projects, venvs, data |
| `~/www/<domain>/` | Website document root (e.g. `~/www/example.xuss.us`) |
| `~/.config/opencode/AGENTS.md` | Instructions your AI agents read automatically |

The file manager can browse your whole account (up to `/var/www/<user>`), upload files up
to 10 GB each (resumable), edit files, and compress/extract `.zip`, `.tar.gz`, `.7z`, `.rar`.

**Included software (current versions)**

- Python 3.11 (`python3`, `pip3`), Node.js 22 (`node`, `npm` 10), Go 1.19
- PHP CLI 8.2 (websites can use PHP 5.3 → 8.5 per domain)
- MySQL client 8.0 (server databases managed in the panel), PostgreSQL databases
- `git`, `curl`, `wget`, `rsync`, `tmux`, `zip`/`unzip`, `7z`, `tar`, `sqlite3`
- The six AI coding agents (section 8)

**Ports.** Each plan includes a small number of public ports for your own services
(HTTP webhooks, APIs, mini-apps). The count is per-plan (2 on Basic → 20 on Elite) and
managed from the panel. Common local ports (e.g. 3000) are usable for internal services;
public exposure is granted by the panel's port system.

**Websites.** Add domains in the panel, point an A record to `149.50.116.15`, and use the
Domains tab to set the PHP version/handler per domain. Node/Python websites can be served
as custom services or reverse-proxied. New domains default to CGI PHP 7.4.

---

## 8. Pre-installed AI coding agents

Every hosting ships with six AI coding agents. Type the command over SSH/web terminal.
Each stores its session/token data inside your own home directory — your credentials stay
yours and are not shared with other accounts.

| Command | Agent | Notes |
|---------|-------|-------|
| `opencode` | opencode (open source) | Full TUI agent for coding tasks. Strategy: needs ~700 MB–1 GB RAM per instance. |
| `mimo` | MiMo Code | Xiaomi's coding agent. |
| `claude` | Claude Code (Anthropic) | Requires an Anthropic account; OAuth sign-in on first run. |
| `codex` | Codex (OpenAI) | Requires an OpenAI account. |
| `agy` | Antigravity CLI (Google) | Google OAuth on first run; preconfigured to reach Gemini from this server. |
| `hermes` | Hermes Agent (Nous Research) | Lightweight (~240 MB) — the best choice for Basic plans. |

**First-run sign-in.** These agents need your own provider account or a free account:

- **Hermes**: register a free account at https://portal.nousresearch.com and run
  `hermes auth add nous` (interactive: paste the token/complete the flow). Or connect your
  own API keys (`hermes auth add anthropic|openrouter|openai-codex|...`).
- **opencode / MiMo / Claude Code / Codex**: run the agent, then follow its login flow
  (`/login` or the provider picker). An agent can also be given a provider API key in its
  config.
- **agy (Antigravity)**: opens a Google OAuth URL on first run. On a headless server, the
  standard flow is to forward the shown localhost port over SSH
  (`ssh -L <port>:localhost:<port> ...`) and complete the Google login in your own browser,
  or paste the authorization code back into the CLI. Session tokens are stored per-user;
  to switch accounts remove `~/.gemini/antigravity-cli/antigravity-oauth-token` and run again.

**Using agents effectively**

- Start with a sensible project directory: `mkdir ~/projects && cd ~/projects`.
- Agents run as your user with your permissions — their file edits and shell commands
  happen inside your account.
- Keep one heavy agent instance per SSH session on small plans.
- Agents can drive `run` themselves (start/reload services, read logs) — tell them to use it
  for anything long-running instead of `nohup`/screen hacks.
- You are billed by your provider for model usage, except the built-in panel assistant
  (section 9), which is billed from your XUSS balance.

---

## 9. Panel AI assistant (built-in, per-token billing)

For accounts with access, the panel (menu → **AI Agent**) includes a built-in assistant
that can read/write files and run commands in your hosting. It is billed **per token**
from your XUSS balance:

- Input, output, and cached-token prices are shown in the agent's model picker.
- Your balance updates live during a response; each run's cost appears on the token meter.
- If the balance runs out mid-run, the run stops — top up and continue.

Availability is controlled by the platform (some features are enabled per account).
The agent is reached at `/panel/agent`; direct link appears in the menu when enabled.

---

## 9b. AI API (OpenAI-compatible, `/v1`)

Accounts with access can also use XUSS AI models from **any OpenAI-compatible client**
(opencode, Cursor, Cline, LibreChat, LangChain, the OpenAI SDKs, …):

- **Base URL**: `https://xuss.us/v1` — create a key in the panel (menu → **AI API** / `/panel/api`).
- **Auth**: `Authorization: Bearer xsk-…` (keys are shown once and stored only as a hash).
- **Endpoints**: `GET /v1/models`, `POST /v1/chat/completions` (streaming and non-streaming;
  tools/function-calling, vision `image_url`, `response_format` JSON, system prompts),
  `GET /v1/tools`, `GET /v1/skills`.
- **Server tools (opt in per request)**: send `"xuss_tools": true` (or a subset array) and the
  server runs read-only tools for you — `web_search`, `fetch_url`, `browser_render` (open/read a
  URL in a real headless browser) and `read_skill` (load a built-in skill doc: `product-design`,
  `telegram-bots`, `cybersecurity`, `databases`, `seo`, … 30 skills). No file/DB/hosting access —
  those stay with the account owner.
- Keys support an optional **expiry** and a **spend limit**; usage is billed **per token from your
  balance** and itemised on the AI usage page.
- Full docs: https://xuss.us/ai-api.md (or the docs site `docs-ai.xuss.us`).

---

## 9c. Telegram account connection (optional, for the AI agent)

You can connect **your own Telegram account** to the panel AI agent so it can read your dialogs and
send messages on your behalf:

- Connect from AI agent → Settings → Telegram account (phone → login code → 2FA password).
- The login session is stored **only inside your own hosting directory** (owner-only permissions);
  codes and passwords are never logged or stored.
- Disconnect any time to log out and delete the stored session — there is no "logout command",
  disconnecting (or deleting the session file) is the switch.

---

## 10. `run` — keep bots and services online 24/7

`run` turns a script into a supervised long-running service: it auto-restarts on crash,
starts after server reboots, obeys your plan's CPU/RAM limits, and shows in the panel's
**Processes** view.

```bash
run python3 bot.py            # start a Python script as a service
run node server.js            # start a Node script as a service
run status                    # list your services (name, PID, state)
run logs bot.py               # follow the service's output
run reload bot.py             # restart the exact same command (after code edits)
run stop bot.py               # stop it
run delete bot.py             # remove the service entry
```

Tips:
- Run this from the directory containing the script; the exact command is remembered.
- Use `run reload` after editing code (it preserves arguments, env and log redirection).
- Processes are visible/managed in the panel too (pause, resume, reload, delete, logs).
- Services count toward your plan's limits — one heavy agent + heavy bot on a small plan
  is a recipe for slowdowns.

---

## 11. Databases

- **MySQL 8** and **PostgreSQL** databases on localhost. Create databases and users in the
  panel (host `localhost`; MySQL port 3306, PostgreSQL 5432).
- Per-plan database count (from 10 up to 200) is listed in `/api/plans`.
- Credentials are viewable in the panel; backups include your databases.

---

## 12. Domains, DNS, SSL

- **Add a custom domain**: Domains tab → add → point your domain's **A record to
  `149.50.116.15`**. The platform provisions the site and DNS zone.
- **DNS management**: full record editor (A, AAAA, CNAME, MX, TXT, NS) per domain.
- **SSL**: one click per domain — free Let's Encrypt certificates, auto-renewed.
  Works for the hosting's own subdomain and custom domains.
- **Deleting a domain** removes it completely (site + DNS + certificate) so the same domain
  can be re-added later, even on another XUSS account.
- **PHP version** is selectable per domain (5.3 → 8.5; new domains default to CGI PHP 7.4).

---

## 13. Email, FTP, cron

- **Email**: create mailboxes on your domains; webmail (Roundcube) and IMAP/SMTP
  (`mail.<your-domain>`, ports 993/465 SSL). Mailbox credentials can be viewed/changed in
  the panel. Outbound sending is disabled by default (anti-abuse) — request it via support.
- **FTP**: create FTP accounts (host = your domain, port 21). Passwords viewable in the
  panel; change them anytime.
- **Cron**: schedule commands with presets or custom 5-field expressions. Cron jobs run as
  your user.

---

## 14. Backups

Every hosting has a **Backups** tab:

- **Create backup now** — copies site files + the site's databases.
- **List / download / restore / delete** individual copies.
- **Schedule** — daily backups at a chosen time (default 04:00) with a retention count
  (default: keep 7 copies).

Use backups before risky changes (deploys, migrations, mass edits).

---

## 15. Subdomains (free)

- Register `your-name.xuss.us` or `your-name.xsss.us` free of charge (weekly quota:
  10 registrations per rolling 7 days; deleted names still count for the window).
- Target can be an **IP address** (auto A/AAAA records) or **NS hostnames** (delegation;
  NS1 required, NS2 optional).
- Edit targets and delete subdomains anytime; they live until you remove them.
- Reserved names (www, mail, ns1-ns4, api, admin, etc.) are rejected; availability is
  checked live against DNS and the platform registry.
- The feature can be disabled platform-wide; the panel shows a notice if so.

---

## 16. Hosting transfers

You can hand a hosting to another XUSS account: the recipient confirms with a 5-digit code
sent by email. Transfer changes **ownership only** — nothing is deleted or moved, and the
SSH password is rotated for safety. Find it under Dashboard → Transfer.

---

## 17. Resource limits & performance

Your plan's **RAM and CPU limits are enforced** for your SSH sessions and your `run`
services. Consequences to expect:

- If your combined usage exceeds the plan's RAM, things slow down dramatically — new
  commands can take a long time to start, and agents may appear "frozen". This is memory
  pressure, not a crash: close unused programs/agents and it recovers.
- If CPU usage exceeds the plan's share, processes are throttled — interactive programs
  stutter.
- Bot crash loops consume limits for no benefit — use `run logs` to see why a service is
  restarting, fix the cause, or `run stop` it.

**If an AI agent seems frozen**
1. Close other agent instances (`Ctrl+C`, `/exit`, close `tmux` windows you forgot).
2. Check `run status` — heavy services may be eating the plan.
3. On Basic, switch to `hermes`; for opencode/agy use Pro or higher.
4. If it still fails, open a ticket — include the command you ran.

---

## 18. Security & privacy

- Each hosting is isolated; your files, databases and processes are not visible to other
  customers.
- Passwords: strong-password policy enforced. SSH password can be rotated in the panel
  ("Change Password").
- 2FA: optional TOTP for your panel account; email+password verification for resets.
- Payments: XUSS never stores card numbers/CVVs; crypto invoices are handled by
  @CryptoBot; Stars by Telegram.
- Data: EU datacenter (Warsaw). See the Privacy Policy: https://xuss.us/privacy
- Never run agents with credentials you cannot afford to expose, and keep secrets out of
  world-readable files.

---

## 19. Support

- **Tickets**: panel → Tickets (attachments supported). Replies arrive by email/Telegram.
- **Telegram**: https://t.me/xussm — fastest for short questions.
- **Email**: support@xuss.us
- **Bot**: @xussnotifybot — notifications and Telegram Stars top-ups.
- Typical response time: a few hours.

---

## 19b. Community chat

The panel has a public **community chat** (menu → Community / `/panel/community`) where all signed-in
XUSS users can post messages, images, videos and files, reply, edit/delete their own posts and see
who is online.

- It is a normal **public chat** (not end-to-end encrypted) — never post secrets, keys or passwords.
- Media is uploaded to XUSS storage and served through unguessable links so it can play inline.
- Admins can mute/block/remove content to keep it safe. Reply notifications (email/Telegram) are
  sent only when someone replies to you.
- The feature can be disabled platform-wide; the menu item disappears when it is.

---

## 19c. Android app

An optional Android app (Android 10+) is available at https://xuss.us/xuss.apk. It is a thin
WebView wrapper around the same website — the same account, cookies and data, no separate data.
Sideloaded builds show the standard "unknown developer" Play Protect prompt.

---

## 19d. Free plan & plan retirement

- **Free plan**: `$0`, one per user, forever (cancelling does not reset it). It renews automatically
  and **cannot be transferred** to another account. Its 256 MB RAM is enough for `hermes` and light
  sites, but not for opencode/agy/Claude Code.
- **Paid plans** can be **paused** (hidden from new orders) or **retired** (existing hostings get an
  upgrade deadline) by the platform operator. If a plan you are on is retiring you will see a banner
  and can upgrade to any available plan at any time.

---

## 20. Machine-readable entry points

All public, no authentication:

| Endpoint | Contents |
|----------|----------|
| `https://xuss.us/agents.md` | This guide |
| `https://xuss.us/llms.txt` | Short index of these resources |
| `https://xuss.us/ai-api.md` | OpenAI-compatible AI API docs |
| `https://xuss.us/api/plans` | Live plans, prices, limits (JSON) |
| `https://xuss.us/api/articles?lang=en` | Knowledge Base index (also `ru`, `uz`) |
| `https://xuss.us/api/articles/{id}?lang=en` | Full Knowledge Base article text |
| `https://xuss.us/sitemap.xml` | Public URLs |
| `https://xuss.us/robots.txt` | Crawler rules (this file is advertised there) |

The Knowledge Base covers every feature in depth — SSH, file manager, databases, backups,
subdomains, domains/SSL, payments, AI agents, `run`, suspension policy, and more.

---

## 21. Guidance for automated agents

- **Registration requires a human** (captcha). Do not attempt automated sign-ups.
- `/panel/*` and `/admin/*` require authentication and are excluded in `robots.txt`.
- Cache `/agents.md`, `/llms.txt` and API responses politely; rate limits apply
  (shared per-IP limits on all endpoints).
- Prices/limits change over time — always read `/api/plans` rather than hardcoding.
- Inside a customer's hosting, prefer documented tools: `run` for services, official
  agents for coding tasks, panel APIs are not exposed for direct customer use (SSH is the
  programmatic interface).
- Do not run more heavy agent instances than the plan's RAM allows (section 3).
- No warranty of uninterrupted availability; report platform issues via support.

---

## 22. FAQ

**Can I run a Telegram bot?** Yes — `run python3 bot.py`. It stays online 24/7 and restarts
automatically.

**Can I use my own domain?** Yes; point an A record to `149.50.116.15`, add it in the panel,
and issue free SSL.

**Is SSH included?** Yes, full SSH on every plan, plus a web terminal in the panel.

**Which AI agent should I use?** On Basic: `hermes`. On Pro: one of opencode/agy/Claude
Code/Codex (one instance). On Max and above: multiple agents comfortably.

**Why did my agent freeze?** Almost always plan RAM exhaustion from one or more heavy
instances — see sections 3 and 17.

**How fast is setup after payment?** Under a minute — website, SSH, and databases are
provisioned automatically.

**How do I pay from an Uzbek card?** Card Transfer tab (send the exact shown amount within
12 minutes) or Click/Payme/Paylov/Uzum.

**Can I transfer my hosting to someone else?** Yes — Transfer from the dashboard;
ownership moves, nothing is deleted, SSH password rotates. Free plans are not transferable.

**Is there a free plan?** Yes — `$0` (256 MB RAM, 384 MB NVMe, 0.15 vCPU), one per user forever,
renews automatically, not transferable, upgradeable to any paid plan at any time.

**Can I use XUSS AI from my own app or editor?** Yes — the OpenAI-compatible API at
`https://xuss.us/v1` with a per-user API key from the panel (AI API). Billed per token from your balance.

**Do you keep backups?** You control them: on-demand copies + a daily schedule (7 kept by default)
in the Backups tab, with one-click restore.

**Is there a community chat?** Yes — a public chat in the panel for all XUSS users (messages,
images, video, files). Public, not end-to-end encrypted; don't post secrets.

---

## 23. Glossary

- **Panel** — the web control center at xuss.us/panel (sites, files, databases, billing).
- **Hosting** — your account on the platform with its own `usr_*` login, disk space,
  limits and websites.
- **`run`** — the command that registers a script as a supervised 24/7 service.
- **Agent (AI)** — one of the pre-installed coding assistants (opencode, hermes, …), or the
  built-in panel assistant.
- **Grace period** — the 14 days after expiry during which data is retained.
- **Subdomain** — a free `name.xuss.us` / `name.xsss.us` registration.
- **Balance** — prepaid USD credit used for all purchases and AI usage.
