One active contract
The website uses one ordered 19-agent registry for names, routes, hosts, statuses, and artwork state.
About Automix AI
A focused roster, built one product at a time.
Automix AI is designing specialist workspaces for clear business roles. Wavy, our WhatsApp customer-engagement workspace, is the first available product. The other eighteen roles remain transparent previews while their workflows and safeguards are developed.
19 specialist rolesOne active registry with a defined role and status for every product.
1 available productWavy is available; every other role is labelled as a preview or repository pending.
Human reviewConsequential messages, payments, and professional-domain outputs stay bounded.
What we are building
Specialists with clear jobs and visible limits.
A useful specialist should make the brief, expected result, review point, and limits easier to understand—not hide them behind a generic chat box.
Each Automix role is defined around a specific job: customer engagement, strategy, writing, search, sales, analysis, recruitment, operations, or another bounded workflow. Preview pages explain the planned inputs, outputs, handoffs, and safety boundary before a backend is promoted.
Wavy is the current working focus. Its public and workspace surfaces are being validated against real provider states, tenant isolation, consent, message receipts, and human approval. Other products stay Coming soon until their own frontend, backend, security, and deployment gates pass.
Operating principles
Truth before breadth.
These principles guide the website, product states, and release process.
Honest availability
A page or API stub is not a live product. Availability requires working software, tests, deployment, and approval.
Original work
Research can inform capability coverage, but Automix copy, visuals, interactions, and identities must remain original.
Reviewable actions
Campaigns, payments, external writes, and professional-domain outputs need visible human control.
Provider-aware states
Queued, accepted, delivered, read, failed, unconfigured, and unavailable are treated as different states.
Release evidence
Builds, tests, browser checks, tenant isolation, DNS, TLS, and rollback evidence are part of completion.
What we do not claim
No borrowed identity. No fabricated proof.
Automix does not copy competitor mascots, page designs, proprietary mechanics, testimonials, or claims. Public research is used to understand user needs and coverage—not to reproduce another company’s product or brand.
We do not invent customers, performance metrics, integrations, prices, professional credentials, or regulated outcomes. Where content, assets, provider setup, or legal review is unfinished, the site should say so plainly or keep the route out of public navigation.
Questions
How to read the Automix roster.
Which product can I use now?
Wavy is the only product currently marked Available. It still depends on your own WhatsApp and optional provider configuration for live messaging, AI, payments, and other external services.
What do the other agent pages represent?
They are product previews. Each describes a planned role, workflow, review gate, and safety boundary; it does not imply that a working backend or integration is live.
Why show nineteen roles before they are all available?
The registry makes the intended product map visible and testable while development stays sequenced. Status labels prevent the roadmap from being mistaken for current functionality.
How are sensitive domains handled?
Health, legal, accounting, banking, financial, employment, and other consequential workflows retain explicit human and professional review boundaries. Preview content is not professional advice.
Start with the workspace that is available.
Explore Wavy’s public experience, then create a workspace when you are ready to configure your own channel and providers.