Klippfy API Terms of Use

Last updated: September 24, 2026

These terms apply in addition to the general Terms and Conditions when you access the Service through the Klippfy API (the /api/subir endpoint and other documented endpoints) using your own API key.

1. Access and API keys

• Your API key is personal and non-transferable. You are responsible for keeping it secure; if you believe it has been compromised, let us know and we will revoke it.
• API keys are stored hashed in our systems — not even Klippfy can see your full key after it has been issued. If you lose it, you need to generate a new one.
• Do not share your API key publicly (code repositories, client-side apps, etc.). Klippfy is not responsible for unauthorized use resulting from a key exposed on your end.
• Mandatory architecture — the key always stays server-side: if you integrate the Klippfy API into your own application so that your own end users ("End Users") can use it, your Klippfy API key must live only in your backend, never in the browser, the mobile app, or any code that runs on your end user's device. The correct flow is: your end user → your application → your backend (with the API key) → Klippfy → result → your backend → your end user. Klippfy is not responsible for charges, abuse, or leaks resulting from exposing your key on the client side.

1.1 Using the API inside your own application ("Customer Application")

You may build your own application or product that uses the Klippfy API internally and that your own end users use through that application (for example, offering clip generation as a feature inside your own SaaS). This is permitted, under the following conditions:

• Your end users access Klippfy through your application, never directly through the Klippfy API with your key or with a key of their own that you distribute to them.
• You are responsible for ensuring that your own terms of service toward your end users include obligations equivalent to those in this document and in Klippfy's general Terms and Conditions — in particular, the prohibited-content rules (section 4 of the Terms) and responsibility for the rights to the content they upload (section 4 of this document).
• What is not permitted without Klippfy's prior written authorization is offering, as your product, raw access to Klippfy's infrastructure (or, indirectly, to the AI providers Klippfy uses — Google Gemini, OpenAI, fal.ai, Modal) with no added value of your own — that is, reselling the computing capacity itself instead of a feature within your own product. If that is your business model, write to us so we can evaluate a specific commercial agreement.

2. Rate limits

• API usage is subject to rate limiting per API key and IP, in order to protect the Service's infrastructure.
• The specific limits for your plan are documented at [TO COMPLETE: link to the API's technical documentation] and may change without prior notice in response to detected abuse.
• Usage via the API draws from the same processing-minutes/credits quota of your plan as usage from the web interface.
• Klippfy may apply additional limits, or temporarily suspend access, if your usage pattern generates a disproportionate cost with the underlying AI providers (Google Gemini, OpenAI, fal.ai, Modal) relative to your plan.

3. Acceptable use of the API

The same restrictions from section 4 of the Terms and Conditions apply (prohibited content, impersonation, etc.). In addition, you may not:

• scrape, reverse-engineer, or attempt to extract the underlying models, prompts, or credentials used by the Service (including those of the providers Google Gemini, OpenAI, fal.ai, or Modal);
• resell raw access to Klippfy's functionality without added value of your own, except with explicit written authorization (see section 1.1);
• use results obtained via the API (clips, captions, transcripts, generated audio or video) to train, fine-tune, or evaluate your own or third-party AI models, without Klippfy's explicit written authorization;
• deliberately exceed rate limits by using multiple accounts or keys to evade rate limiting.

4. Liability for third-party content

If you use the API to process content that belongs to a third party (for example, you integrated Klippfy into your own application and your users upload videos), you are solely responsible for having the necessary rights and consents over that content vis-à-vis those third parties — including the consent of the people whose voice, likeness, or face appear in it, per section 4 of the AI Policy. This also applies with respect to the AI providers that process that content on Klippfy's behalf (Google Gemini, OpenAI, fal.ai, Modal — see AI Policy, section 2): their own terms require whoever submits data to hold the necessary rights over it, and that responsibility falls on you as the integrating developer. You agree to indemnify and hold Klippfy harmless against any third-party claim arising from content you process through your integration, including reasonable legal fees.

No guarantee of originality of results: results generated through generative AI features (video, image, avatars, voice, music) are not guaranteed to be original or free of third-party rights — see section 3 of the Terms and Conditions.

5. Availability and changes

The API is provided "as is," subject to the same liability and availability limitations described in sections 7 and 9 of the Terms and Conditions. We may introduce breaking changes with reasonable advance notice by email or in the technical documentation.

6. Revocation

We may suspend or revoke API access immediately in the event of misuse, without prejudice to the other measures described in the general Terms and Conditions.

7. Contact

Klippfy — [TO COMPLETE: full legal/company name and registered address in Mexico] — [email protected]