Support

toolweight is a small, independent project. There is no ticket queue and no bot: mail reaches a person, and corrections reach the dataset.
A number looks wrongThat is the most useful thing you can tell us, and it has its own path. Every cell on every table has a dispute link that opens a prefilled public issue naming the exact tool and field. Corrections are made in the open, and the issue stays as the record.Suggest a correction
A tool is missingSay which tool and which comparison it belongs in. Coverage is editorial, so not every suggestion lands, but every one is read.Suggest a tool
How a score is worked outScores are a weighted mean over normalised field values, not an editorial ranking. The methodology page explains the normalisation, the confidence levels and what coverage means.Methodology
The API or the MCP serverBoth are public, need no key, and are licensed CC BY 4.0. The JSON API is versioned in the path so its shape can change without breaking you. The MCP server is streamable HTTP at toolweight.com/mcp.The JSON API
Your account, saved profiles or billingSaved weight profiles, score alerts and the Pro plan all live on your account page, including the link to manage or cancel a subscription. Cancelling keeps your profiles; only the caps come back.Your account
The iOS appThe app reads the same public data as the website and signs in to the same account. If a comparison looks stale in the app, pull to refresh: content is cached per session and re-fetched on the next launch.

Reach a person

Email hello@toolweight.com. Expect a reply within a couple of business days. For anything about the data itself, a public issue is faster and leaves a trail everyone can read.Source and issues: github.com/aussieljk/toolweight. Maintainer: me@lucasknight.com.au.