Terms of Service

Welcome to Jame Agent OS ("the Service"). By authorizing your self-hosted n8n/Make workflows to run webhook requests through the Service gateway, you agree to comply with and be bound by the following legally binding Terms of Service.

1. Operational Model and Dependencies

Jame Agent OS is a high-availability, stateless middleware gateway. It formats and proxies outbound HTTPS requests matching trigger payloads from developer platforms like n8n, Airflow, or Make directly to social platform network channels.

• Third-Party Dependency: You acknowledge that our service speeds and operational uptimes depend directly on the availability of the official Meta Developer APIs.
• No Hosting of Credentials: You are solely responsible for securing your own Access Tokens. You must never hardcode token credentials in public files or non-secure relays.

2. Authorized Use & Acceptable Policies

You agree to use Jame Agent OS strictly in compliance with all official developer rules and regional laws.

• Prohibited Conduct: You shall not utilize the gateway to distribute spam, fraudulent coordinate schemes, explicit media, unauthorized trademark materials, or harmful malware.
• Security Escapes: You are prohibited from attempting to bypass the rate-limiting firewalls or reverse-engineer the system node routers.

3. Disclaimer of Warranties

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE." TO THE FULLEST EXTENT PERMISSIBLE BY LAW, WE EXPRESSLY DISCLAIM ALL REPRESENTATIONS AND WARRANTIES. WE MERELY FORWARD TRANSIT PAYLOADS AND DO NOT CONTROL THE ACCURACY, COMPLIANCE, OR DELIVERY OUTCOMES OF DESTINATION GRAPH ENDPOINTS.

4. Direct Limitation of Liability

IN NO EVENT SHALL JAME AGENT OS, ITS DEVELOPERS, OR ASSOCIATES BE LIABLE FOR ANY CONSEQUENTIAL, INCIDENTAL, SPECIAL, OR EXEMPLARY DAMAGES ARISING OUT OF THE EPHEMERAL TRANSMISSION OR LOSS OF CONNECTIVITY TO THE META DEVS SYSTEM.

5. Jurisdiction and Support

These terms shall be governed by applicable laws in Texas, United States of America. Any disputes or clarifications can be filed directly to our primary developer contact: