Spare Cycles Terms

Draft for legal review. Keeta Workspace prepared this draft, and it has not yet been reviewed by counsel. Text in [square brackets] needs a decision from counsel. Remove this note when the document is published.

Last updated: [date of publication]

These terms add to the Terms of Service for organizations that turn on Spare Cycles in Keeta Workspace: lending idle connected agents to other organizations, borrowing theirs, or using the Compute API. Each is off until an owner or admin turns it on.

1. Lending

1.1 What it is. When an organization lends, Workspace may give its idle connected agents tasks from other organizations that borrow. A lent agent takes borrowed work only while it has nothing of its own to do, one task at a time.

1.2 Your plan. By enabling an agent to lend, you confirm that its model plan and the provider's terms allow it to work for other companies, and that you have the right to use the computer it runs on this way. That is your responsibility, not Keeta's.

1.3 The borrower's data. While a lent agent works on a borrowed task, your computer holds that task's text and code. You must not access, copy, keep, use or disclose it except to do the task through Workspace; the Workspace Runner deletes it when the task ends, and you must not get around that. Workspace never tells you which organization the work is for. You are responsible for keeping the computer secure.

1.4 Earnings. You earn the share of the borrower's price set out in the Credits and Billing Terms and shown in Workspace (currently half of OpenRouter's listed price for the model your agent used), paid as credits to your organization's balance once the borrower's payment is confirmed. Credits are not cash and follow the Credits and Billing Terms.

2. Borrowing

2.1 What it is. When an organization borrows, a task none of its own agents can start may be offered to other organizations' lent agents for a short time, before its Hosted Agents take it.

2.2 Lenders see your work. By turning borrowing on, you accept that the lender's computer, outside Keeta's and your control, will see the borrowed task's text and code, and you instruct Keeta to send it there. Lenders are bound by section 1.3, and agents run sandboxed without the lender's own tools, but don't turn borrowing on for work you aren't willing to share this way. Tasks in confidential teams, tasks given to an agent by name, and tasks needing tools on a person's own computer are never offered.

2.3 Price. Borrowed work costs the Workspace rate plus the lender's price, as the Credits and Billing Terms describe.

2.4 Your data protection duties. A lender is not Keeta's subprocessor: it processes the borrowed task on your instruction to share it. Before borrowing, make sure you may share the task's content this way, including any personal data in it. [Counsel: confirm the processor analysis, and whether lenders need a direct agreement with borrowers.]

3. Compute API

Organizations may call lenders' local models through Workspace's Compute API with keys they make. What is sent reaches the lender's computer, as in section 2.2. Calls are priced as Workspace shows, and may fall back to OpenRouter unless you turn that off.

4. No guarantee

Spare Cycles depends on other organizations' computers being online. Keeta does not guarantee that capacity is available, or the quality, speed or result of any lender's work beyond what Workspace's verification checks.

5. Ending

An owner or admin can turn lending, borrowing or the Compute API off at any time; work in progress then ends or returns to its pool. Keeta may stop an agent from lending, or an organization from borrowing, to protect other customers or the Service.