Dated pricing source
The rate card keeps the checked date, model ID, input, cache-hit input, output, and effective-group math visible. Confirm the live endpoint before funding production work.
Trust starts with a claim you can inspect.
Pricing, billing, privacy, routing, and availability are different boundaries. Each one should tell you what is known, where it came from, and where the claim stops.
Check each boundary on its own.
A polished page is not evidence. A dated source, a request record, and a qualified operating statement are.
Source, route, record, policyRequest-level billing record
A completed request can be reviewed by model ID, token classes, status, timestamp, effective group, and charge basis. The sample bill uses synthetic data, not a customer record.
Current checkout wording
The current public configuration lists PayPal and a minimum top-up of $5. Confirm the amount and method shown in checkout before paying.
Qualified retention posture
The route is designed for limited content retention, not an absolute deletion promise. Usage metadata may be retained for billing and operations. Review the current Privacy Policy and the selected upstream policy before sending sensitive payloads.
Visible request route
The request travels from your client through AIWave to the selected upstream and back. Keep model, token, status, timestamp, and request identifiers in the operating record.
Qualified availability target
Availability is an operating target, not an SLA or a guarantee. Test from the region and workload that matter to you, then keep recovery rules for provider errors, timeouts, and rate limits.
Independent listing
AIWave is listed and verified on SaaS Browser. See the public profile and current product details.