Acceptable use
This policy applies to customers, providers, API keys and anyone using capacity obtained through AgentRanking. It supplements, and does not weaken, the terms of service and model licenses.
Prohibited activity
- Distributing malware, ransomware, credential stealers, botnets or destructive payloads.
- Unauthorized access, scanning or disruption of systems you do not own or have permission to test.
- Child sexual abuse material, non-consensual intimate imagery, or content that violates applicable law.
- Escaping workspace isolation, or attempting to reach provider devices or other workspaces' data.
- Interfering with the provider agent, signed command protocol, metering, or routing controls.
- Using model outputs in violation of the model's published license or applicable rights.
- Reselling capacity in a way that hides the actual user, payment source or abuse contact.
- Automated attacks on the API, rate limits, deposit scanner or authentication challenges.
Customer responsibilities
You must secure prompts, API keys and uploaded files, rotate exposed credentials, and delete data you no longer need. Treat every response as untrusted content and do not execute model-generated tool calls without your own authorization.
Provider responsibilities
Providers must keep device enrollment credentials private, report accurate hardware and readiness, honor maintenance and drain behavior, and not inspect workspace prompts or artifacts beyond the documented operational interface. Provider access to a request is bounded by the accepted policy.
Enforcement
The operator may suspend a workspace, API key, provider device or payout, freeze new spend, or preserve evidence for investigation. Enforcement decisions are recorded with a reason where practical. Resource suspension is separate from financial reconciliation; neither is represented as a completed refund.
Reporting abuse
Report suspected abuse through the support channel in the console with the affected resource ID, timestamps and any safe evidence. Do not send credentials, private keys or third-party personal data.
This policy is operator-owned content. The server enforces authorization and isolation even when a client interface permits an action.
