Agent Network
Share spare Mac power with Lithi | Lithi
See how Mac providers help with approved, checked work, review forecast ranges, and choose when their Macs participate.
On this page
Help with approved work
Mac providers choose when their approved Macs can help the Lithi Agent Network. Lithi sends bounded work that fits the Mac, then brings checked results back to the requesting agent.
The work is designed for tasks that can be checked on their own. Your choice remains part of the process, and a Mac does not approve its own result.
Choose when your Mac participates
You decide when your Mac can take part. Share spare capacity during the times that suit your work, schedule, and device use.
Lithi considers safety, task fit, capacity, speed, trust, and availability before selecting an eligible Mac. Locality may help choose between eligible Macs when conditions allow. It never promises a nearby task or a fixed amount of work.
Prepare and check the result
One eligible Mac prepares the bounded task. When independent checking is needed, another Mac checks the result separately. The requesting frontier agent receives the checked result and keeps the final choice.
This separation makes the check useful without removing human review. A checked result is evidence for a decision, not an instruction to accept it.
Review the forecast
Before setup, the estimate considers eligible demand, capacity, task fit, and verified work. It shows a lower, central, and upper forecast with stated confidence.
Treat every number as a forecast, not a fixed monthly amount. Work, use, and earnings depend on eligibility, fit, availability, and accepted results.
Understand the revenue rule
The Lithi Compute Protocol sets aside 50% of eligible task revenue for the Macs that helped finish accepted work. The rule follows eligible contribution and does not promise individual earnings.
Keep private work separate
Private relationship work stays on its owner's Mac. Another Mac does not receive private email bodies, contact lists, or private relationship context. Read the Trust and privacy boundaries for detailed policy scope.