Read a Compute impact report
Read the Work, energy and community sections of a monthly Compute impact report, with evidence labels, coverage, and limits kept clear.
See your accepted work and recorded Mac participation
See the work completed and the Macs recorded as helping produce it. Your monthly account-period report can show accepted work, recorded Mac participation, physical activity, and energy or emissions where the evidence supports them. Check the account, period, revision, and method before using a figure.
When you get it
Your report covers the month's recorded work and remains separate from the paid purchase invoice and credit and usage statement. Buying credit does not itself create measured impact. You can open the report in your Compute account, and an agent with reporting permission can read it through the Impact Reports API. Electricity and emissions figures are marked measured, estimated or unavailable; an unavailable figure is never shown as zero. The report records what happened. It isn't a bill or a savings claim.
The current report contract keeps three participation populations separate:
| Report population | Contract field | What it tells you |
|---|---|---|
| Macs recorded with accepted work | accepted_work_macs | Macs linked to accepted work in the report population. |
| Macs recorded with physical activity | physical_activity_macs | Macs with recorded physical activity, which can include work that failed or was retried. |
| Provider accounts recorded with participation | provider_accounts | Provider accounts linked to the report population, including participation beyond accepted work; an account can represent a person or an organization. |
These populations can overlap, but they are not additive totals. A provider-account count is not a verified human count, and none of these fields establishes the scope of a provider or the complete participation population. Do not infer either from a different count.
Here is an illustrative reading example. The values are examples only, not customer measurements:
Mac participation in your month's work
accepted_work_macs: 12
physical_activity_macs: 18
provider_accounts: 6Read the account period as a monthly record, not as a per-task dashboard. A missing value is not zero. The report explains the physical activity covered by its evidence and the population each figure uses.
Read the report through its reporting path and permission. That access is separate from Work tools and job keys; reporting is not a sixth Work MCP tool.
How your work and Mac participation are recorded
Before a task starts, Lithi checks whether the assigned Mac is allowed and able to run it. A Mac that runs the work can record the time it worked and any available energy readings.
A task does not have to succeed to use electricity. A failed attempt, a retry, or a separate result check can contribute to the energy record, even when the result is rejected. If a task is rejected before it starts, it is not counted as an attempt that ran. Checks made before the task can still use electricity, but that energy needs its own supporting record.
Lithi checks whether the result meets the task's requirements. Separately, it checks whether the energy evidence can support a figure in the report. The report keeps its three reader sections clear:
| Section | Read for | Keep separate |
|---|---|---|
| Work | Accepted outcomes, useful units, activity covered by the section, and excluded outcomes. | Attempts, jobs, accepted units, and billing units use different denominators. |
| Energy and emissions | Measured or estimated electricity, emissions, units, observation period, method, and coverage. | Physical activity can include unsuccessful work; unavailable energy or emissions is not zero. |
| Community | Contribution time, broad regions, eligible allocations, and confirmed payments. | A noncash allowance, allocation, device count, or contribution time is not cash. |
The machine-readable report keeps Work and energy as distinct groups. Work counts accepted outcomes; energy covers physical intervals, including failed and unpaid work. Energy and emissions remain separate components even when the reader view presents them together.
How to read the energy evidence
The information available depends on the participating Mac and the supported measurement method. Lithi may use:
- the Mac's model, or the group of similar hardware it belongs to;
- information about how the work ran and which software release was used;
- energy readings tied to a defined period of time;
- temperature or power-state information, when the measurement method needs it; and
- a broad electricity-grid region, where permitted and needed for the calculation.
The report keeps measured, calibrated, estimated, and unavailable evidence distinct. These labels explain how a reading or estimate can be used:
| Reader label | What it means |
|---|---|
| Meter reading | A meter measurement, with a clear record of what was measured and how much activity it covers. |
| Calibrated Mac reading | A reading from your Mac, checked against an appropriate electricity meter and used only within the conditions validated by that check. |
| Calibrated estimate | An estimate based on supported records of how the work ran, using a calibrated energy-use profile with a recorded version. |
| Uncalibrated reading | A recorded signal that is not enough, on its own, to report an electricity figure. |
| No usable measurement | There is not enough usable measurement information. This does not mean no electricity was used. |
Not every Mac directly measures the electricity used by each task. A reading can still be useful without supporting an electricity figure. Keep the unit, denominator, activity covered, observation period, method version, and omissions attached to any figure.
For an example involving a failed attempt, a retry, and a result check, read the impact methodology. The example explains the calculation; it is not a reading from your Mac or a billing rule.
How Lithi avoids counting electricity twice
One energy reading can cover several activities. Lithi works out each activity's share using the recorded activity and the stated allocation method. For electricity used while the platform gets ready or waits for work, the method can use overlapping periods of customer activity.
Lithi keeps the energy used by the Mac (device_load) separate from the energy drawn from the grid
(grid_input). When a grid-input figure already includes the Mac's electricity, Lithi counts it
once. It does not add the Mac's figure on top.
Why the electricity region matters
To estimate emissions, Lithi needs enough information about the electricity-grid region to choose the right emissions factor, the figure used to convert electricity use into an emissions estimate. Your exact home address, bank address, or an unrelated business address is not a substitute for evidence of that electricity region.
When the required region information, emissions factor, or energy checks are missing, the affected report value stays unavailable. Customer reporting region, execution or grid region, and provider business region are different facts. A provider address or broad reporting region does not prove where work ran.
The report may also keep embodied hardware impact and managed infrastructure as separate components. Infrastructure can include control services, database and queue, artifact storage, and network transfer. A covered subtotal is not a complete footprint when a required component or factor is unavailable.
Keep community value and cash separate
Mac contribution may appear as time or a contribution allowance. It is noncash and does not create a provider payout or referral payout. Where provider value is reported, 50% of eligible settled task revenue is allocated to the provider pool for Macs that helped complete accepted work. That is an allocation basis, not 50% of an invoice or a promise of individual earnings, local economic retention, or payout. Lithi uses the rest of the revenue, with no percentage set, to run the network (finding and billing customers, routing and checking every task, support and payouts) and to grow it, including social media ads planned and checked with its own Meta Ads kit. Shares are before costs, not profit.
Contribution work can still use physical resources and electricity. A provider allocation or accrued value is not a confirmed payment, and an energy figure does not show how much anyone has earned or confirm that anyone has been paid. Keep allocation, individual earnings, payment, and claimed savings separate.
Share a figure with its identity
Keep the report period, revision, snapshot digest, evidence label, unit, denominator, activity covered, method, factor source, boundary, and omissions with the figure. Corrections create a new revision with lineage to the earlier snapshot; they do not silently rewrite it.
For the calculation boundary and claim rules, read the Compute impact methodology. For exact retrieval, fields, typed availability states, and report identity, use the Compute Impact Reports API. If a report or field is missing or disputed, use the impact report recovery guide.