Anonymous per-month counts of real browser interactions, agent/MCP calls, direct API calls, and corrections. Declared QA and load-test traffic is excluded. No IPs, accounts, client IDs, or session identifiers — how this works. ← Back to the tool
This report groups recorded ParaMat activity by month and filament. It covers browser lookups and exports, agent and API requests, and submitted corrections. The month selector loads the available aggregate counts from the public telemetry service.
Counts represent recorded events, not unique people, printed parts, material tests, or product performance. Browser activity is counted only when visitors opt in. Agent and API activity is reported separately, and declared QA and load-test traffic is excluded.
An empty report means no recorded events are available for that month; it does not establish zero use. If the telemetry service is unavailable, the report explains the limitation. These activity counts do not validate the strength emulator or establish physical print performance.
These are activity counts, not unique people. Browser counts come only from visitors who opt in; MCP and API counts are automatic, aggregate-only requests; flags come from anyone tapping "🚩 Looks wrong". Counts are approximate (best-effort). Telemetry never stores search text, barcodes, receipt contents, preflight request contents, IPs, user agents, client identities, or session identifiers. Raw real-use JSON: /top · License CC BY 4.0.