Everything about latest.sh happens in the open, in the repository that holds the data. Pick the channel that matches what you need — they all land in the same place and are read by a human.
The fastest fix is a pull request against the tool’s JSON file — include a link to the vendor’s pricing page so it can be verified. If you would rather not open a PR, file an issue with the tool name and what changed. Corrections are the most useful thing anyone sends.
Open an issue with the product name and its pricing URL. Tools that publish clear, public pricing are quickest to add; anything behind “contact sales” for every tier is harder to represent honestly.
Same channel, and corrections from vendors are welcome — you know your own pricing better than anyone. The
durable fix is to publish a pricing.md file on your own domain: the registry reads it
directly, your entry stops depending on anyone re-checking it by hand, and it is worth the largest single share of
your transparency score.
Start with the developer docs, which cover the MCP endpoint, the REST API, and every machine-readable file. If something there is wrong or missing, that is a bug — please report it.
The single ad slot is sold through Carbon — enquiries go to carbonads.net, not here. Buying an ad does not affect any listing, ranking, or score.
The repository is at github.com/rogermbyrne/pricing.md, maintained by Roger Byrne.