Hosted Agent Runtime Schedule
One-page addendum to an executed Master Service Agreement. Last updated July 8, 2026.
This Schedule attaches to the executed Master Service Agreement (/legal/msa.html) between Agentics Technologies LLC and Customer, and applies only if the Order Form includes the Hosted Agent Runtime. Capitalized terms come from the MSA. If this Schedule conflicts with the MSA, this Schedule controls for hosted-runtime matters only.
- Agentics executes Customer-approved agent workloads on Agentics-managed infrastructure inside Customer's tenant boundary.
- Same governance, same ledger: every hosted-agent model call passes through the gateway under Customer's policies, budgets, and guardrails, and produces chained receipts exactly as self-hosted traffic does. Hosting never bypasses governance.
- The MSA's no-training clause, security commitments, liability cap, and data-ownership terms apply unchanged to hosted workloads.
Hosted workloads run within the quotas in the Order Form (concurrent agent runs, CPU/memory per run, maximum run duration, storage, and egress). Runs exceeding a quota are throttled or terminated, and each such enforcement is itself recorded as a receipt. Quota increases are made by Order Form amendment.
| Area | Agentics | Customer |
|---|---|---|
| Runtime infrastructure, patching, isolation | Responsible | — |
| Policy enforcement, receipts, anchoring | Responsible | — |
| Agent selection, configuration, and approval | — | Responsible |
| Policies, budgets, and guardrail settings | Enforces as configured | Defines |
| Data submitted to and produced by agents | Processes per MSA/DPA | Owns; controls categories sent |
| Credentials granted to hosted agents | Stores encrypted; uses only as scoped | Issues, scopes, and rotates |
| Model-provider agreements for Customer-supplied keys | — | Responsible |
| Availability of the runtime (per MSA Section 5) | Responsible | — |
This Schedule runs with the Order Form that includes it and ends when that Order Form or the MSA ends. On termination, in-flight runs are allowed to complete or are stopped safely at Customer's election, and hosted-run data follows the MSA's 60-day export window. Questions: /contact/.
Terms · Privacy · MSA · DPA · Partner Platform Agreement · Hosting Addendum