Public pilot · Operating terms

Advice first.
Execution only after approval.

AuraUnited is in a controlled public live test. These plain-language operating terms explain the current boundaries. Payments for credit packs are live and processed by Stripe as described below; formal commercial terms will continue to evolve with the pilot.

Payments and refunds

Credit packs are one-time purchases in EUR, processed through the Stripe hosted checkout. Listed prices exclude VAT where applicable; the checkout always shows the exact total, including any tax for your location, before you confirm. A completed payment grants the stated credits to your signed-in account. There is no subscription, no recurring charge and no stored payment authorisation. A self-service refund is available within 24 hours of purchase and removes the purchased credits. Never share card details with anyone claiming to represent AuraUnited; payments happen only on the Stripe checkout page.

Human responsibility

Plans, repository reports and suggested actions are advisory. Customers must review important decisions, verify generated instructions and maintain backups before changing software, accounts or production systems.

Inquiry routing

AuraUnited can route signed-in, credit-metered inquiries to owner-configured providers. The current consensus runs its three voices and synthesis on the Groq free-tier API when configured, falling back to free OpenRouter routing for two voices and GPT-5.6 Sol for the premium voice and synthesis. A provider-backed function fails closed when its dedicated credential is missing.

No automatic repository changes

The current GitHub pilot requests no write permission. AuraUnited cannot create branches, commits, pull requests, deployments or external messages from the repository-comprehension surface.

Availability and change

Pilot functions, limits and prices may change as reliability and cost evidence is collected. AuraUnited may pause a model-backed function instead of exceeding its stated cost or safety boundary.

Acceptable testing

Do not submit repositories or information you are not authorized to use. Do not use the pilot to expose credentials, evade access controls, cause harm or make high-stakes decisions without a qualified person.