Legal · Acceptable use
Acceptable Use Policy
MetaBlox Code may be used only for lawful, authorized, and reasonably supervised software engineering activities.
1. Authorization boundaries
You may access, test, or modify only code, repositories, accounts, devices, and systems that you own or are expressly authorized to use. You may not expand the scope of authorization, conceal unauthorized activity, or retain unrelated data.
2. Prohibited unlawful and harmful activity
- Malware, ransomware, credential theft, phishing, fraud, spam, denial of service, or botnets.
- Unauthorized exploitation, privilege escalation, persistence, surveillance, data theft, or security-control bypass.
- Infringement of intellectual property, privacy, trade secrets, or other legal rights.
- Weapons, violent extremism, child sexual exploitation, human trafficking, or other serious harm.
- Unlawful surveillance, discrimination, impersonation, false documents, or manipulative commercial conduct.
3. No resale, sublicensing, or general-purpose proxying
You may not resell accounts, sessions, Credits, or access capabilities; share access outside your organization; provide a general-purpose Model Interface, proxy, forwarding, or aggregation service; enable third-party indirect use through recharge, wrappers, shared quota, or similar methods; or evade account review or real-user identification.
4. No model extraction or distillation
You may not systematically collect prompts, outputs, reasoning, tool traces, or evaluation data to train, fine-tune, distill, copy, replace, or improve another model. Extracting system prompts, safety classifiers, internal model information, or using multiple accounts to evade detection is prohibited.
5. Responsibility for agents and tools
You are responsible for actions performed by agents through terminals, browsers, code repositories, and connected systems. You must maintain human oversight, least privilege, task budgets, and the ability to stop execution, and must review all changes before deployment.
6. Identity, region, and account integrity
Registration information must be truthful. You may not use false identities, proxy accounts, multiple accounts, payment instruments, or network locations to evade regional, enforcement, rate, or other controls. After permanent termination, you may not register again or borrow another person’s account.
7. Monitoring and enforcement
The operator may use automated and human review to detect abnormal usage, fraud, resale, model extraction, and security threats and may block requests, reduce limits, require verification, suspend, or permanently terminate accounts. Serious or continuing violations may be acted on without prior notice.