# Getting started with Automix What every Automix product shares: one workspace, one credit wallet, and one place to see what you have spent. Read this once, then pick the product you actually came for. _Takes about ten minutes._ ## Before you start > **Before you start** > > You need an Automix account with a verified email address, and a browser. Nothing else — no card, no developer app, no API key. Every step on this page works on a brand-new workspace. > **Don't have a provider account yet? You don't need one.** > > Connecting WhatsApp, a social network or a phone number happens inside the product that uses it, not here. This guide gets your workspace ready first. > > [See the documentation index](/docs) ## Watch the setup _The setup video has not been recorded yet._ ## 1. Verify your email address Sign up, then click the link in the verification email. Verification is not cosmetic: the signup credit grant is withheld until the address is verified, and it is granted exactly once per workspace when it is. If you verify later, the grant still happens — it is not lost by verifying out of order. ## 2. Check your credit balance Your workspace has one wallet, shared by every Automix product. The balance is shown in the top bar of the app and is served by a single endpoint, so what you see in one product is what you have in all of them. > **One wallet, every product** > > There is no per-product balance to keep in your head. A ledger row records which product spent what, but the money is in one place. ## 3. See what an action costs Prices are published by the billing API and are the same for every caller, so you can read them before you have an account. Nothing in this documentation states a price: the rate card is data, and quoting it here would be a copy that goes stale the first time it changes. ## 4. Pick the product you came for Wavy is the WhatsApp product, Socie the social one, Wani the voice one. Each has its own documentation, its own setup guides and its own connect flow. Some of what they do needs a provider credential and some does not. Wavy's shared team inbox, for instance, works on a new workspace with nothing configured — the capability table is the honest answer for each one, and every product's docs page renders it. > **Read your product's docs next** > > Each product page lists what works today, what needs a credential, and the real routes. > > [Wavy documentation](/docs/wavy) ## 5. Watch what you spend The usage page reads your own ledger and shows what was spent, when, and by which part of the product. An empty range renders as empty — there is no fabricated baseline and no flat line drawn through no data. ## 6. If you run Automix yourself Self-hosting is a different job from using the product. The backend reads its configuration from environment variables; the two below are the ones nothing starts without. Their values live in your deployment's environment file and are never printed by the application. Environment variables: `DATABASE_URL`, `LLM_API_KEYS` ## After connecting - Your wallet balance appears in the top bar of every product. - Each spend writes one ledger row naming the operation and the product. - The usage page groups those rows by day, and by operation when you ask it to. ## Next - [Wavy documentation](/docs/wavy) - [Socie documentation](/docs/socie) - [Wani documentation](/docs/wani) --- Status: reviewed · reviewed by gemini-3.8-flash Author: claude-fable-5.1