Service accounts dashboard

Open Service Accounts to see connected services first, with balances, plan usage and the date each source was checked. The page fits desktop and phone screens. Provider directory lists other services you can track; its count does not mean you have an account with every provider.

Live USD balances includes only current dollar balances. Native credits, other currencies, invoices, customer balances and internal credit pools remain separate. Balance coverage compares fresh balance readings with discovered connections. Accounts found includes discovered connections and your saved records. Other teams, organizations and subscriptions may still be missing.

Use Track an account for another organization, product or subscription. Record its name, plan, billing merchant, renewal date and budget. For example, a Supabase product billed by Vercel keeps Supabase as the service and Vercel as the merchant. A manual balance carries the date you checked it. Keep credentials and card details out of account notes.

Supported readings

PassBook reads these balances on the dashboard host with the keys you already saved, the same way its own Balances page does, and gives the dashboard numbers only. Balance checks are read-only and respect their existing permissions. Each check appears in PassBook’s activity as “read service balances”. If PassBook on the host is too old to read balances, each card says so: update PassBook, then refresh.

Plan allowances and invoices are not cash balances. Vultr’s accounting amounts are shown without assuming they are spendable funds. Bankr’s wallet balance covers its API keys collectively. An OpenAI connection can be healthy while its prepaid balance remains unknown.

QuiverAI billing uses a separate organization Admin key with billing-read permission. Project keys cannot read organization billing, and Admin keys cannot run inference. Connect billing key opens secure setup in the current page and keeps your inference key separate. It accepts a key you already have; it does not create credentials or change provider permissions. If PassBook is not connected, review that connection before entering a key. The billing-key form does not use the legacy key editor.

Scrape Creators charges one credit for a balance check, so automatic checks are disabled. UsePod reports balance with paid requests; the dashboard does not make a paid request solely to obtain a balance. Alchemy needs separate admin usage permission. For services without a supported reading, use the official account link and retain a dated manual record.

Refresh and access

Refresh balances checks eligible connections. A refresh within 30 seconds can return the previous successful reading, and PassBook can return a reading up to two minutes old when the same key made it. A changed key is always checked afresh. Readings become stale after five minutes. If a refresh fails, a previous amount keeps its original date and is excluded from live totals and top-up estimates. The page does not automatically poll providers.

Encryption alone does not mean a saved key is unavailable. If existing key access is denied, Review secure keys opens the usual PassBook flow in this page. Review only the access you intend, then refresh. A provider may separately require billing permission even when inference works.

When a provider rejects a future billing read, the dashboard retains its HTTP status and a safe category: authentication rejected (401) or access denied (403). These distinguish the response types, but do not establish whether the cause is an invalid key, missing permission, an IP restriction or account state. Provider error bodies and credentials are not displayed.

Use your existing private Tailscale or Hivemind Link connection to reach the dashboard from another authorized device, then open Service Accounts. The host must serve the current dashboard, and the usual dashboard sign-in still applies. Device access and network configuration are managed by your existing installation.

A Link peer address beginning with 127.0.0.1 requires Link running on the device where you open it. That local Link forwards the connection to the dashboard host. A direct Tailscale hostname instead requires that device to belong to your authorized Tailnet and the host to expose a working dashboard route, including its page assets. These addresses have different prerequisites; changing the hostname alone does not make a Link address a direct browser address.

Plan a top-up

For prepaid or mixed billing, choose a planned purchase amount. A fresh dollar balance can calculate the amount needed to bring it to $100. This is a budget choice, not a spending forecast. No estimate is calculated from a stale balance, invoice, unknown amount or native credit unit.

Review billing shows the service, planned amount, currency and payment destination. Continuing opens its official site. The planned amount is not submitted to the service; confirm the correct account, amount, currency, minimums, fees and payment method at checkout. Opening or cancelling the review makes no charge. Return after paying and refresh the balance.

External provider charging is not integrated. OpenRouter’s former Coinbase Commerce purchase endpoint is deprecated. xAI documents a management top-up endpoint, but direct charging remains unavailable here until payment identity and duplicate-charge reconciliation are supported. See OpenRouter’s endpoint notice and xAI billing.

The separate HivemindOS internal credit accounts section retains wallet funding. Its review identifies the account, USDC amount, Base network and wallet before payment. A settled retry returns its receipt. Pending or unknown results block another payment until reconciled. Issue internal credits is a separate action that makes no purchase. No card details are stored.

See what consumes each service

Open View activity on a service, or use the activity filters to compare applications, dates, and request outcomes. Request details include available agent, task, run, session, model, provider request, and account information. Daily and weekly totals use UTC. Refresh activity to see the latest observations, and load older requests to continue through the retained history.

Activity begins when this version of the app is used. It records direct supported provider calls from chat, voice, trading analysis, photo keywording, Shared Brain embeddings, skill distillation, Fusion panels, and web search. It does not read prompts, responses, files, keys, card details, or credential URLs into the log. Browser realtime sessions, external agents and apps, scripts, and provider-console activity can still be missing. Connected media apps and hosted services may make provider requests outside this app. An empty activity view does not prove there was no usage.

Unknown cost is shown as unknown. OpenRouter’s reported costs retain their native credit unit. Other costs require a verified provider cost source; token counts alone are not an invoice. Purchases, subscriptions, API consumption, and customer balances are kept separate. Credit auto-reload is a funding rule rather than a usage cap.

Existing company ledgers and Hermes session counters appear under Existing ledger & runtime evidence. They are never added to the request totals. Session counters cover the entire session; their date is its end/start, not a request timestamp. Existing budget observations and reservations are not verified provider bills. Earlier charges cannot be assigned to jobs where no attribution was recorded.

Activity is workspace scoped, readable only through the existing owner authentication, and retained for up to 90 days or 20,000 journal records. Interrupted requests can remain pending. Retry attempts remain individually visible; repeated provider request IDs are excluded from consumption totals. Logging failures are reported as coverage gaps and do not change the service operation.