API Terms

1. Access and credentials

Access is limited to the account, application, scopes and endpoints Mirai authorizes. Keep keys server-side, restrict access and rotate compromised keys promptly. Do not share credentials across unrelated customers, evade rate limits, scrape protected references or bypass a disabled property. Contact Mirai if the issued scopes do not cover your proposed integration.

2. Authorization and licence scope

Submit accurate application, asset and use information. A successful technical response, downloaded reference or generated draft is not permission to publish. Before distribution, obtain the required licence, payment confirmation and approvals for the specific asset, territory, channel and term. Training, voice replication, unrestricted sublicensing and endorsements are not included unless expressly authorized.

Permission may expire or be withdrawn for future generation. Respect denials and expiry, and re-check authorization when required by the integration agreement. A prior successful check does not authorize new uses indefinitely. Existing licences are governed by their own continuation and termination terms.

3. External rendering and publication

Rendering on another provider requires a separately approved integration and processing scope. Do not send restricted reference assets to unapproved providers or end users. Report outputs, content hashes and external identifiers accurately where the integration requires them. A usage report or signed credential records a decision; it is not a blanket warranty about every pixel or every underlying right.

Your application must enforce publication holds and moderation requirements. Prompt controls are not a guarantee of output compliance. Where human review is required, the output must remain private until approved.

4. Usage and billing

Generation allowances, overages, licence fees and settlement timing follow the account plan or signed order form. Retried requests must follow endpoint-specific idempotency requirements. Do not assume that a timeout means no job or charge was created; check job status before submitting another chargeable request. Reconcile disputed usage using the request and licence identifiers.

5. Data, caching and provenance

Use reference assets only for the authorized request and retain them only for the agreed period. Do not use them to build a reusable model, dataset or competing likeness library. Apply the agreed deletion and access controls, including to your subprocessors. Execute a DPA where required.

Do not remove draft watermarks or misrepresent an unlicensed output as licensed. Preserve required attribution, credential links and provenance information where technically supported. Make visible AI disclosures where the licence or applicable law requires them. No certification or content-signing feature is promised unless available in the contracted service.

6. Service changes and remedies

Mirai may suspend affected access for security, non-payment, rights restrictions or misuse. Breaking changes, support and service-level commitments follow the integration agreement; no uninterrupted availability or model-specific latency is guaranteed by this page. Warranties, liability and dispute handling follow the executed agreement and applicable Terms of Service. Report security or integration issues to info@mirai.inc and rights concerns to legal@mirai.inc.