1. Agreement and Parties

These API Terms of Service ("API Terms") govern access to and use of the Atomiser Partner API (the "API"), operated by Gautam Rajanand trading as Atomiser ("Atomiser", "we", "us"), a sole proprietorship based in India. They apply to any company or entity ("Partner", "you") that accesses the API on behalf of itself or its end users ("End Users").

By creating an API key, making an API call, or permitting End Users to invoke the API, you accept these API Terms. If you have a separately signed agreement with us, that agreement prevails to the extent it conflicts with these API Terms.

2. The API

The API provides programmatic access to Atomiser's AI content-processing tools — including transcription, subtitles, clips, reframing, audio enhancement, repurposing, text-to-speech, dubbing, file conversion, and social publishing — through an asynchronous job model described in the developer documentation at atomiser.ai/developers. Available tools may vary per Partner depending on the agreed plan, and not all tools are available to every Partner.

3. API Keys and Security

API keys are issued per Partner and per environment (test or live). Keys must be stored server-side and never embedded in client-side code, mobile apps, or shared publicly.
You are responsible for all activity under your keys, including activity by your End Users.
Notify us immediately at contact@atomiser.ai if a key is compromised; we will revoke and reissue it.
Webhook secrets returned by the API must be treated as credentials and used only to verify deliveries.
We may rotate or revoke keys for security reasons, with notice where practicable.

4. Plans, Credits and Billing

API usage is metered in credits. Each tool consumes credits at the rate published in the developer documentation and in the GET /v1/tools response. Unless otherwise agreed in writing:

Each paid plan includes a monthly credit allowance that refreshes on the billing date.
Unused credits do not roll over to the next billing period.
Usage beyond the monthly allowance ("overage") is billed at the overage rate stated in your order or plan confirmation, invoiced monthly in arrears. Overage applies only where it has been enabled for your account.
Optional add-ons — including the social publishing capability — are billed as stated in your plan (for example, a monthly platform fee plus a fee per connected social account). Connected-account counts are reported through GET /v1/api-usage so billing is independently auditable by you.
Failed, cancelled or timed-out jobs are not billed. For multi-asset tools, only successfully generated assets are billed.
Invoices are payable within the period stated on the invoice. We may suspend API access for undisputed invoices overdue by more than 15 days.
Fees are exclusive of taxes. Applicable GST or other taxes will be added as required by law.

5. Usage Records

Our metering records are the authoritative record of credit consumption and connected-account counts for billing purposes. You can query your consumption in real time via GET /v1/api-usage, broken down by tool and by End User reference. If you believe a billing period's metering is inaccurate, raise it within 30 days and we will investigate and correct any error.

6. White-Label Rights and Resale

Subject to these API Terms, you may:

Integrate the API into your own product and offer the resulting features to your End Users under your own brand — no Atomiser attribution is required;
Set your own pricing to End Users, independent of our rates;
Use your own End User identifiers (end_user_ref) so that no End User personal data need be shared with us.

You may not resell raw API access itself, share your keys with third parties, or present the API as your own infrastructure. References to Atomiser in your own public materials require our prior written approval, except for accurate factual references in internal documentation.

7. Partner Obligations

You are responsible for:

Your own terms with End Users. You must maintain terms of service and a privacy policy with your End Users that pass through the acceptable-use requirements in Section 8.
Content rights. You must ensure that every item of content submitted to the API — by you or your End Users — is content you or the End User owns or is licensed to process, and that all required consents (including likeness and voice consent where relevant) have been obtained.
End User conduct. End User violations of these API Terms are treated as your violations.
Platform compliance. For publishing tools, you are responsible for compliance with each destination platform's own terms (e.g. YouTube, Instagram), including obtaining required End User authorisations for connected accounts.

8. Acceptable Use

You must not use the API, and must not permit End Users to use it, to process:

Content you or the End User does not have rights to process;
Adult or sexually explicit material;
Deepfakes or synthetic media depicting real individuals without their explicit consent, or content designed to deceive about authenticity;
Misinformation, incitement, harassment, or content promoting illegal activity;
Content infringing intellectual-property, publicity, or privacy rights.

You must also not: attempt to reverse-engineer or extract the API's underlying models or providers; exceed agreed rate limits or attempt to circumvent metering; probe, scan or test the API's security without permission; or use the API to build a directly competing general-purpose content-processing API. We may suspend processing of content that violates this section and terminate access for material or repeated violations.

9. Service Operation

Asynchronous processing. Jobs are queued and processed asynchronously; typical durations per tool are published in the documentation. Processing times vary with source length, demand, and tool.
Results. Job results are delivered via signed URLs valid for a limited time (currently 24 hours, refreshed on each read). Persist results on your own storage if you need them beyond the URL lifetime.
Timeouts. A job exceeding its maximum processing window is marked failed and is not billed.
Changes. We may update tools, models, and credit rates. We will give at least 30 days' notice before a rate change takes effect for existing Partners.
Availability. The API is provided on a commercially-reasonable-efforts basis. No uptime SLA applies unless separately agreed in writing.

10. Data Handling

Content submitted through the API is processed solely to deliver the requested outputs and to operate, secure, and improve the service. In particular:

We do not require End User personal data — end_user_ref may be an opaque identifier of your choosing;
Submitted media and generated outputs are retained for the periods described in the developer documentation and our Privacy Policy;
We manage the underlying AI supply chain end-to-end. Processing may involve carefully selected third-party infrastructure and AI providers under confidentiality and data-processing obligations consistent with this section;
We do not use your or your End Users' content to train models for the benefit of other customers, and we do not sell submitted content.

11. Intellectual Property

You and your End Users retain all ownership of submitted content. Outputs generated for you by the API are yours to use and distribute without restriction. To the extent any output requires a licence from us, we grant you a perpetual, worldwide, royalty-free licence to use it for any lawful purpose.

The API, its documentation, the Atomiser name and marks, and the underlying platform remain our exclusive property. These API Terms grant no rights in them other than the limited right to access the API as described.

12. Confidentiality

Each party agrees to protect the other's non-public technical and business information obtained through the API relationship — including keys, webhook secrets, and unpublished technical details — with reasonable care and to use it only for the purposes of this relationship. Publicly available information, including our published rate card and documentation, is not confidential.

13. Warranties and Disclaimers

THE API IS PROVIDED "AS IS" AND "AS AVAILABLE". TO THE MAXIMUM EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. AI-GENERATED OUTPUT MAY CONTAIN ERRORS; YOU ARE RESPONSIBLE FOR REVIEWING OUTPUTS BEFORE PUBLISHING THEM.

14. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW: (A) NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR LOST PROFITS, REVENUE, DATA, OR GOODWILL; (B) OUR TOTAL LIABILITY ARISING OUT OF OR RELATING TO THE API IS LIMITED TO THE FEES YOU PAID US IN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM. THESE LIMITS DO NOT APPLY TO LIABILITY THAT CANNOT BE LIMITED BY LAW, OR TO YOUR PAYMENT OBLIGATIONS.

15. Indemnity

You agree to indemnify and hold us harmless from claims, damages, and expenses (including reasonable legal fees) arising out of: (a) content submitted through your account, including claims that it infringes third-party rights or lacks required consents; (b) your or your End Users' violation of these API Terms or applicable law; or (c) your breach of your obligations to your End Users, including claims by End Users relating to the API features you provide them.

16. Suspension and Termination

Either party may end the API relationship with 30 days' written notice. Prepaid fees for the current billing period are non-refundable except where we terminate without cause.
We may suspend access immediately for material breach, security risk, unlawful use, or non-payment, with notice where practicable.
On termination, keys are revoked. Usage records and accrued billing through the termination date remain payable. Sections 7, 11, 12, 13, 14, 15 and 17 survive termination.

17. Governing Law

These API Terms are governed by the laws of India. Disputes will be subject to the exclusive jurisdiction of the courts of New Delhi, India, unless a signed agreement between us states otherwise.

18. Changes to These Terms

We may update these API Terms. For material changes we will provide at least 30 days' notice via email to your registered contact or via a notice on the developer documentation. Continued use of the API after the effective date constitutes acceptance. If you do not agree with updated terms, you may terminate under Section 16 before they take effect.

19. Contact

For questions about these API Terms or the API relationship, contact us at: contact@atomiser.ai