Developer and API Addendum

Effective Date: September 8, 2026

This Developer and API Addendum ("Addendum") supplements the 67idea Terms of Service and applies when you access the developer dashboard, APIs, SDKs, API keys, or related developer services. If this Addendum conflicts with the Terms of Service concerning Developer Services, this Addendum controls.

1. Organizations and authority

If you use Developer Services for an organization, you represent that you have authority to bind it. The organization is responsible for its projects, members, applications, credentials, and end users. Owners and administrators must remove access promptly when it is no longer authorized.

2. API credentials and security

Secret API keys are confidential credentials. You must store them only on trusted servers or approved secret stores, use the least permissions needed, separate test and live credentials, and revoke exposed or unused keys promptly. You may not embed secret keys in public source code, browser code, distributed mobile applications, logs, or client responses. You are responsible for activity performed with your keys until they are revoked or we disable them.

3. Customer applications and end users

You are responsible for your applications and their users, including providing legally sufficient notices and obtaining required rights and consents for content and personal information submitted to the Service. Do not submit regulated or highly sensitive data unless we have agreed in writing that the Service supports it. External user identifiers must be pseudonymous and must not contain secrets or unnecessary personal information.

4. Tools and output contracts

The MCP-backed tool catalog and its schemas may change. You must discover and validate current schemas and handle errors safely. Fixed product endpoints have their documented contracts. Unless separately agreed, previews, beta features, test environments, and dynamically discovered tools have no service-level agreement and are not for safety-critical or mission-critical uses.

5. Uploads, workspaces, and published media

Workspaces are isolated by project, environment, and external user. You may access only media and paths assigned to the authenticated workspace. Upload and published-media URLs may be short-lived credentials; do not expose them unnecessarily. The Service is not an archival system. You must independently retain results you need.

6. Fees, balances, and usage

Developer/API pricing may differ from web-app pricing. Current prices, units, limits, and taxes are those presented in the developer dashboard, API documentation, order form, or other written agreement. We may reserve estimated funds before execution and settle the actual charge afterward. Failed or canceled work may release a reservation, but completed or third-party processing may remain chargeable as disclosed. Test and live environments may have different billing treatment.

7. Limits and fair use

You must comply with quotas, concurrency limits, and rate limits and may not evade them through multiple accounts, organizations, projects, keys, or identities. We may throttle requests to protect users, capacity, security, or Service integrity.

8. Prohibited uses

You may not probe tenant boundaries, gain unauthorized access, distribute malware, conceal abusive automation, resell access without permission, or build a service that materially violates applicable law or another person's rights.

9. SDK and documentation

Subject to these terms, we grant a limited, revocable, non-exclusive, non-transferable license to use our SDKs and documentation solely to integrate with the Service. Pre-release interfaces may change without notice. Open-source components remain under their applicable licenses.

10. Monitoring and suspension

We may monitor metadata and usage necessary to secure, operate, support, and bill the Service. We may suspend credentials, projects, or organizations when reasonably necessary for abuse, security risk, nonpayment, legal requirements, or material violations.

11. Data protection

Our Privacy Policy describes our processing as a service provider. You remain responsible for your privacy obligations and instructions to us. A separately executed data processing addendum or enterprise agreement controls where applicable. This Addendum is not a data processing addendum.

12. Contact

Questions may be sent to support@4014labs.com.