@PaulD1 some clarifying content in the snippet above. Using the HTTP action card offered by the SharePoint connector (see screenshot) does not require the P1 license as it's within SharePoint.
You're right that using the HTTP action card to access other data sources like Cognitive Services will require P1 going forward, however the spirit of this move is not to monetize gaps in functionality that should be included in Office. Any gaps in the current connectors, especially in Office 365 data sources, should be resolved in the connectors themselves so that the broadest possible set of users can take advantage of them without having to use the more advanced HTTP triggers. This is part of why there is a long extension to current users of these features to make sure we can properly close gaps.
It would be much more reassuring to just make it so that any HTTP call to any Microsoft Service does not require the additional licensing costs. After all, if we are accessing an MS Service (such as Cognitive services) we are already paying for that service via Azure. There seems to be a significant lag between new features being added to services and those features being exposed in the relevant Flow actions, so 'properly closing the gaps' is a continually moving target.
I would also like to see an alternate 'per use' option made available - an example, we have deployed an app which uses HTTP calls to Google translate (as Bing translate does not cover all the languages we need) - it will likely only be used occassionally. It would be good to have an option to pay per call (instead of the blanket extra cost per user regardless of how much the feature is used).