Service-Specific Terms

Last updated: June 19, 2026

These Service-Specific Terms apply to particular AveMujica API features and supplement the Terms of Service. If these terms conflict with the general Terms of Service for a specific feature, these Service-Specific Terms control for that feature.

1. API access and model availability

The API service may perform technical processing needed to provide compatible model access, maintain availability, apply safety settings, enforce quota and pricing rules, and protect accounts.

Service processing decisions are not a guarantee that a specific provider, model version, region, latency, price, or output will be used unless expressly agreed in writing.

2. Content, files, and generated outputs

You are responsible for content submitted to the service and for outputs returned by models. You must review outputs before relying on them and must configure applications so users understand when they are interacting with AI-generated content.

Files, images, masks, prompts, outputs, and derived metadata may be processed by supported providers and infrastructure needed to fulfill the request. Record retention and account access to related records may depend on plan, feature, data handling settings, and provider requirements.

3. Fees, balance, subscriptions, and quota

Usage may be billed by tokens, requests, model rules, group pricing, image size, subscription allowance, wallet balance, automatic top-up, or other plan-specific measures. Pricing and quota may differ by group, model, endpoint, provider, and feature.

Usage estimates may differ from final settlement when provider-reported usage, output length, image generation behavior, rounding, service processing, or plan rules affect the final usage record.

4. Access limits and reliability

We may apply reasonable access limits, safety checks, abuse-prevention measures, and availability controls to protect the service.

Some features may use technical compatibility and reliability measures. These measures may affect records, latency, and client-visible response timing.

5. Customer data and retention

Some billing history, order records, security records, abuse records, payment records, and backup records may be retained to satisfy legal, tax, security, dispute, and integrity requirements.

If export features are used, selected data may be delivered to destinations selected for those features. You are responsible for ensuring that any destination you control is appropriate for the data and your compliance obligations.

6. Uptime, maintenance, and support

We aim to operate the service reliably, but do not guarantee uninterrupted access unless a separate written service level agreement applies. Maintenance, provider outages, abuse events, security incidents, payment failures, or capacity constraints may interrupt or degrade service.

Support is provided through the support options and response levels available for your plan. Contact [email protected] for support questions.

7. Changes

We may update these Service-Specific Terms as features, provider requirements, pricing, data handling, safety controls, and service practices change.