Enterprise Terms of Service & Technical Operations Agreement

Opens-Rout grants qualified enterprise developers a non-exclusive, non-transferable, revocable right to connect software agents and external services directly via our RESTful and WebSocket programmatic endpoints.

• Credential Custody: API secret tokens must be stored strictly within secure vault systems and never exposed within public code repositories.
• Endpoint Integrity: Reverse-engineering protocol handshakes, bypassing transport layer proxies, or attacking authentication handlers results in immediate token revocation.
• Telemetry Logging: System ingress and egress payload metrics are logged to monitor infrastructure health, rate anomaly detections, and systemic routing integrity.

Agent tasks executed in sandboxed bash containers run under microVM hypervisors with strict computational boundaries, ephemeral root volumes, and isolated socket boundaries.

• Forbidden Commands: Malicious socket tunneling, kernel exploit injections, mining operations, or network packet sniffing inside execution micro-instances are strictly prohibited.
• Process Lifecycle: Containers persist only for the task duration or until timeout ceilings are met. Temporary file systems purge automatically upon execution completion.
• Egress Whitelisting: Outbound network requests dispatched by container commands must target allowed endpoints declared in your application environment manifest.

Resource access is metered in standardized compute units and language tokens based on processor execution runtimes, model context volume, and memory residency.

• Quota Enforcement: Hard quota ceilings safeguard infrastructure availability. Exceeding assigned burst limits will generate standard HTTP 429 rate responses without queue drops.
• Metering Integrity: Computed allocations are measured in 100-millisecond execution slices. Transparent ledger records are available through your organizational dashboard.
• Overages & Auto-Scaling: Enterprise accounts configuring elastic overflow compute must maintain validated billing methods prior to initiating automated surges.

Customers retain all rights, title, and intellectual interest in the prompts, code routines, enterprise documents, and proprietary outputs processed across the network.

• Zero Model Retraining: Opens-Rout does not ingest private customer payloads, embeddings, or execution scripts to train foundational neural networks.
• Output Ownership: Derived program scripts, autonomous agent summaries, and compiled artifacts belong entirely to the originating enterprise client.
• Platform Mechanics: Proprietary router heuristics, sandbox orchestration engines, and distributed dispatch algorithms remain the exclusive intellectual property of Opens-Rout.

We strive to maintain continuous gateway operations and sandbox availability across regional cluster deployments subject to planned maintenance schedules.

• Uptime Thresholds: Production gateway targets an operational availability benchmark of ninety-nine point nine percent per calendar month.
• Scheduled Maintenance: Essential kernel patches and physical hypervisor maintenance windows are announced at least seventy-two hours in advance through our system status feeds.
• Service Offsets: Documented unplanned outages extending past monthly thresholds are eligible for programmatic service adjustments applied to successive billing schedules.

Either party may conclude service agreements upon written transmission or automated account deactivation according to the parameters specified herein.

• Immediate Suspension: Continued abuse of compute instances, intentional distribution of malicious code, or unpaid balances warrants provisional suspension.
• Data Archival Period: Account owners retain thirty days to export logs and orchestration configurations following an elective account deactivation request.