A plain-language map of Amanai's service, data practices, commercial terms, and operational dependencies.
The short version: Amanai is an independent AI gateway. We route requests to third-party infrastructure, do not persist prompt or response content in the Amanai gateway, and do persist the account, usage, billing, payment, and security records needed to operate the service.
In plain language
- Amanai is a gateway, not the creator of every model. Model and provider names belong to their respective owners and do not imply affiliation or endorsement.
- Inference is dependency-based. A model may be routed through one or more upstream services. Routing can change as capacity, quality, price, or availability changes.
- No permanent model promise. Upstreams can rate-limit, degrade, change prices or policies, discontinue models, or close. We may replace, pause, or retire an offering in response.
- Content is transient at our gateway. Prompt and response bodies are handled in memory to serve the request and are not written to the Amanai gateway database. Upstream services may apply their own practices.
- Operational records remain stateful. Accounts, API keys, sessions, model and token usage, credits, orders, payment identifiers, referrals, promotions, security events, and selected IP records may be retained.
- AI can be wrong. Verify important output. Do not rely on Amanai as a substitute for professional, safety-critical, or emergency judgment.
How a request moves
- Your API key or session is authenticated and limits or available credits are checked.
- The request payload is forwarded to infrastructure capable of serving the selected model.
- A response is streamed or returned to you. Amanai may use fallback routing when a route is unavailable.
- The gateway records non-content usage metadata such as model, token counts, provider route, delivery status, latency, and credits charged.
Read the detailed AI & Provider Disclosure.
What we retain—and what we do not
| Category | Amanai gateway practice |
|---|---|
| Prompt and response content | Processed in memory; not persisted by the gateway |
| Usage and billing metadata | Persisted for accounting, operations, reliability, and disputes |
| Account and OAuth profile | Persisted to provide login and account access |
| Orders and payment identifiers | Persisted for settlement, support, reconciliation, and fraud prevention |
| Selected security and abuse records | May include IP addresses and be retained according to operational need |
“Stateless” describes inference content handling, not the entire platform. See the Privacy Policy for the full distinction.
Availability and service change
We work to keep the gateway useful, but do not promise uninterrupted access or a permanent upstream route. Maintenance, abuse controls, network faults, upstream capacity, provider policy, commercial changes, legal restrictions, and service closure can affect availability. Unless a separate written agreement says otherwise, Amanai provides no service-level agreement.
Policy documents
- Service Terms — the terms governing access to Amanai.
- Privacy Policy — data collected, shared, retained, and controlled.
- Acceptable Use Policy — prohibited activity and fair-use expectations.
- Credits, Payments & Refunds — prepaid credits, QRIS, USDC, failed requests, and refunds.
- AI & Provider Disclosure — routing, upstream dependencies, output limitations, and sensitive data.
- Security and Cookie Notice.
Contact
| General support | support@amanai.dev |
|---|---|
| Billing | billing@amanai.dev |
| Privacy | privacy@amanai.dev |
| Security | security@amanai.dev |
| Abuse | abuse@amanai.dev |