CLOCOT DEVELOPER & API TERMS
Effective Date: October 2, 2026 Last Updated: October 2, 2026
These Developer & API Terms apply when a user accesses or integrates with Clocot through an API, SDK, webhook, developer interface, extension, or other programmatic method. They supplement the Terms of Service.
1. SCOPE
These Terms apply to developers, customers, Organizations, applications, and services that use Clocot programmatically.
2. ACCESS
Developer access may depend on plan, feature availability, account status, region, technical capacity, or separate commercial terms. Not every Clocot function is guaranteed to be available through an API.
3. DEVELOPER CREDENTIALS
Developer credentials are confidential and must be handled responsibly. Customers are responsible for keeping their credentials under appropriate control and for promptly replacing credentials that may no longer be secure.
4. PERMISSIONS
An integration may act only within the permissions granted by the relevant Account, Organization, connected service, and Clocot configuration. Developers are responsible for ensuring that their application has appropriate authority for the data and actions it requests.
5. USAGE LIMITS
Clocot may apply limits relating to requests, concurrency, storage, actions, model usage, or other resources. Developers must not intentionally avoid or undermine applicable service limits.
6. WEBHOOKS AND INTEGRATIONS
When a customer configures a webhook or external integration, the customer directs Clocot to exchange the data needed for that connection. The customer is responsible for the external endpoint, recipient, and configuration.
7. DATA AND PRIVACY
Developers processing personal information must comply with applicable privacy law, provide required notices, honor user rights, and use an appropriate data-processing agreement where required.
8. END USERS
If a developer provides Clocot-powered functionality to its own end users, that developer is responsible for its own terms, privacy notices, support, disclosures, permissions, and legal compliance.
9. AI AND AUTOMATED ACTIONS
Applications using Clocot AI or automation must apply appropriate human review for material uses and must not represent AI output as guaranteed accurate. The developer is responsible for authorization of actions initiated through its integration.
10. SECURITY RESPONSIBILITY
Developers must use reasonable safeguards appropriate to the sensitivity of the data and functions involved and must notify LexLupi promptly if a material compromise affecting Clocot is reasonably suspected.
11. PROHIBITED USE
Developer functionality may not be used for activity prohibited by the Terms of Service, Acceptable Use Policy, or applicable law.
12. RESALE AND WHITE LABEL
API access does not automatically grant a right to resell Clocot as a standalone competing service. Resale, white-labeling, or redistribution that materially substitutes for Clocot may require a separate written agreement.
13. API CHANGES
Clocot may update, version, deprecate, or replace APIs. For stable production interfaces, LexLupi will provide migration information or notice where commercially reasonable. Preview interfaces may change more frequently.
14. FEES AND USAGE
Programmatic use may consume subscription capacity, Clocot Credits, model usage, or other billable resources according to the applicable plan or Order.
15. SUSPENSION AND CONTACT
Clocot may restrict developer access where reasonably necessary for security, abuse prevention, non-payment, legal compliance, service stability, or provider requirements.
Developer questions may be sent to office@clocot.com.
LexLupi LLC Legal Contact: Tatjana Sindjelic