Acceptable Use Policy

This AUP is part of the TrexAPI Terms of Service. By using the Services, you agree to comply with this AUP.

1. Purpose and Scope

TrexAPI provides API infrastructure, proxy routing, TrexID-based memory workflows, credential-binding controls, and related service surfaces. Because these systems can affect downstream providers, shared infrastructure, and customer data flows, misuse is strictly prohibited.

2. Illegal or Harmful Use

You may not use the Services to engage in, support, or facilitate illegal, fraudulent, abusive, or harmful activity.

Prohibited uses include:

• violating applicable laws or regulations;
• promoting or facilitating violence, exploitation, or unlawful surveillance;
• using TrexAPI to enable fraud, impersonation, or unauthorized access;
• processing or routing content in a manner that materially harms others or breaches their legal rights.

3. Malicious Payloads, Malware, and Abuse

You may not upload, transmit, store, fetch, resolve, or distribute malicious payloads or harmful software through the Services.

• malware, ransomware, spyware, worms, or trojans;
• payloads designed to damage, disrupt, exfiltrate, or compromise systems;
• malicious code embedded in prompts, stored payloads, or TrexID workflows;
• content intended to weaponize the proxy or memory layer against third parties.

4. Credential Theft, Phishing, and Social Engineering

You may not use the Services to obtain, harvest, phish, exfiltrate, or misuse credentials, secrets, authentication data, or sensitive account information.

• credential theft or password collection;
• phishing messages or fake login workflows;
• collection of provider API keys or session secrets without authorization;
• social-engineering campaigns, deceptive impersonation, or account takeover attempts.

5. Proxy, Routing, and Memory-Layer Abuse

You may not abuse TrexAPI proxy routes, compatibility layers, TrexID resolution paths, payload storage, or cache retrieval systems.

• using the proxy to hide abusive or disallowed traffic;
• routing unsupported, deceptive, or intentionally masked provider traffic;
• abusing TrexID or payload workflows to replay, scrape, or mass-extract content without authorization;
• using the memory layer as an open relay, data drop, or shared abuse surface.

6. Security Controls, Rate Limits, and Integrity

You may not bypass, disable, interfere with, or probe security or integrity controls on the Services.

• bypassing rate limits, quotas, or anti-abuse protections;
• replaying signed requests or forging metadata;
• probing or exploiting authentication, authorization, or webhook validation behavior;
• attempting to evade auditing, logging, or enforcement controls.

7. Account Sharing and Resale

You may not share, sublicense, resell, or expose the Services in a manner that circumvents our seat, subscription, account, or security model.

• sharing a single account across unrelated organizations;
• reselling shared dashboard or API access without written authorization;
• creating pooled or brokered access that bypasses commercial terms;
• using promo, trial, or discounted plans as an unauthorized multi-tenant resale layer.

8. Enforcement

We may investigate suspected violations of this AUP and take action where reasonably necessary to protect the Services, our users, third-party providers, or the public.

Enforcement actions may include:

• risk scoring or additional verification;
• temporary or permanent rate limiting;
• blocking traffic, routes, models, or credentials;
• revoking API keys, sessions, or TrexID access;
• suspending or terminating accounts;
• cooperating with providers, service partners, or law enforcement where appropriate.

We may act immediately where we believe urgent action is required for security, abuse prevention, legal compliance, or platform integrity.

9. Reporting Concerns

If you believe the Services are being used in violation of this AUP, contact [email protected] with as much detail as possible. We may request logs, request IDs, TrexIDs, account information, or supporting evidence to review the report.

10. Changes to This Policy

We may update this AUP from time to time. The most current version will appear on this page with an updated “Last updated” date. Continued use of the Services after an updated version becomes effective means the updated AUP applies to your use.