Commercial policy

Acceptable use policy

Candidate effective date: 6 August 2026 · Not active until public billing launches

The service coordinates bounded software work; it is not a marketplace, payment service, credential broker, or unrestricted execution environment.

Required use

Customers must configure exact projects, endpoints, permissions, budgets, and provider accounts. They must respect third-party terms, intellectual property, privacy, and access boundaries.

Prohibited use

• Submitting credentials, secrets, payment data, or unrestricted filesystem authority in task payloads.
• Bypassing project isolation, approval, budget, queue, lease, or recovery controls.
• Using the service as a resale marketplace, money transmitter, stored-value product, or provider-account sharing service.
• Automated abuse, malware delivery, unauthorized access, surveillance, deceptive activity, or infringement.
• Representing candidate CLI output as verified production work without review.

Enforcement

We may pause or limit unsafe or abusive activity while preserving relevant audit evidence. Material enforcement and appeal procedures must be finalized before public billing.