STEAM COMMUNITY TOOLS
Methodology
How links are parsed, matched, labeled, and opened.
Typed resource parsing
Every accepted URL becomes one explicit resource type such as Store app, Community profile, Workshop file, inventory, or Market listing. Login, checkout, trade-offer, credential-bearing, and secret-bearing URLs are rejected.
Authored destinations
Outbound URLs are reconstructed in the browser from authored route templates and exact HTTPS host allowlists that ship with the site. A pasted link can only select which authored routes apply; it can never supply a destination.
Route precision
Exact and resolved-exact routes preserve the specific Steam identity you pasted. Search routes prefill a provider search. Contextual routes are related to the resource without being addressed by that exact identity: a provider homepage, a fixed tool page, or a broader profile view. Labels are shown on every card so a contextual route is never presented as an exact match.
Job families
Destinations are grouped by the job they help with: official, research, compatibility, compare, market, community, competitive, and utility. Families organize the list and never imply endorsement or commercial priority.
Terminal catalog states
Every provider has one visible state. Providers without an admitted destination remain cataloged without an Open action.