Acceptable Use Policy
Effective date: March 1, 2026. This policy defines what is and is not permitted on the AgentBuilders platform.
Purpose
This Acceptable Use Policy ("AUP") governs your use of the AgentBuilders platform. It exists to protect the platform, its users, and the broader internet from harmful activity. All users, agents, and deployed applications must comply with this policy.
Prohibited Uses
You may not use AgentBuilders to deploy, host, or distribute:
- Malware and exploits: viruses, trojans, ransomware, rootkits, exploit kits, or any software designed to compromise systems or data.
- Phishing and fraud: fake login pages, credential-harvesting sites, social engineering attacks, or deceptive content designed to steal information.
- Cryptocurrency mining: any application that uses platform compute resources for mining, proof-of-work, or similar resource-intensive cryptographic operations.
- Illegal content: content that violates applicable laws including but not limited to child exploitation material, content promoting terrorism, or regulated substances.
- Spam and bulk messaging: applications that send unsolicited bulk communications, automated spam, or operate as open mail relays.
- Denial-of-service tools: stress testers, booters, DDoS tools, or any application designed to disrupt other services.
- Infringing content: content that violates copyright, trademark, or other intellectual property rights without authorization.
- Harassment and abuse: content targeting individuals with threats, doxxing, stalking, or coordinated harassment campaigns.
Agent-Specific Rules
AI agents deploying applications on AgentBuilders are subject to additional rules:
- Automated abuse scanning: all agent-deployed applications are scanned at deploy time for malicious patterns, prohibited content, and policy violations.
- Auto-quarantine: applications that fail abuse scanning are automatically quarantined and will not be served until reviewed and cleared.
- Rate limiting: agent API calls are subject to per-tier rate limits. Agents that exceed limits will receive 429 responses with retry guidance.
- Identity transparency: agents must identify themselves via API key or bearer token. Anonymous agent deploys are subject to the strictest quotas.
- Human accountability: a human account holder is ultimately responsible for all applications deployed by agents acting on their behalf.
Resource Limits
To maintain platform stability and fairness, all accounts are subject to resource limits based on their tier:
- Maximum number of deployed applications per account.
- Storage quotas for files (R2) and database rows (D1).
- API request rate limits measured per minute and per day.
- Compute time limits for Edge AI and serverless functions.
- Bandwidth quotas for application traffic.
Attempting to circumvent resource limits through multiple accounts, API manipulation, or other means is a violation of this policy.
Abuse Reporting
If you encounter content or behavior on AgentBuilders that violates this policy, please report it to hello@agentbuilders.app with the following information:
- The URL or app name of the offending application.
- A description of the violation.
- Any supporting evidence (screenshots, logs).
We review all abuse reports and aim to respond within 48 hours.
Enforcement
AgentBuilders enforces this policy through a graduated response:
- Warning: for minor or first-time violations, we may issue a warning with instructions to correct the issue.
- Quarantine: applications violating this policy may be taken offline and quarantined pending review.
- Suspension: repeated or serious violations may result in temporary account suspension.
- Termination: severe violations (malware, phishing, illegal content) may result in immediate and permanent account termination.
We reserve the right to take immediate action without prior warning for violations that pose an imminent threat to users, the platform, or third parties.
Changes to This Policy
We may update this Acceptable Use Policy from time to time. Material changes will be posted on the platform with an updated effective date. Continued use of the Service after changes constitutes acceptance of the revised policy.