How does local agent usage differ from a Lumoswitch platform bill?
Distinguish local agent log summaries, platform model-call usage, and official subscription quotas.
Maintained by the 路墨 Lumoswitch product team
Local history is derived from logs that remain on the device and may be incomplete; platform bills cover Lumoswitch service calls. Do not add the two together.
What does local agent usage show?
After you request a scan, the app summarizes logs kept locally by some supported agents, showing parseable tokens and logged costs by local date, agent, and model. It does not upload conversations, read API keys, launch an agent, or send model requests. Deleted logs, format changes, or missing metrics can make results incomplete or unavailable; logged costs are not the same as actual charges.
What does the platform bill cover?
Lumoswitch platform usage and billing correspond to requests processed through the platform runtime and its metering. They do not represent every request made by an external agent on your computer. If an external agent calls a provider directly, use that provider's bill for actual charges; costs in local logs may only be estimates.
How should I reconcile costs?
First identify whether a request used an online platform configuration, a local direct connection, or another external route. Check platform bills and request records for platform calls; compare local agent logs with the provider console for local calls; check the relevant product's official page for subscription quotas. Do not add token counts or USD estimates across views as if they were actual charges, and do not assume external calls are tracked by the platform.