+1

I just assume that EF (as well as most/many of the other tools) was doing some sort of data scraping in order to deliver their product. I know that several other similar products did as well (e.g. KVS). And there could be issues that the data being queried was unusual (like booking class to the exclusion of others).

Going forward, I assume that any new tool or updated version of any of our current tools will have to do everything using the same access paths that OTAs, GF, etc use. And pay like everybody else does. I have always wonder if some sort of shortcutting to get access to data while avoiding costs did not lead to the downfall of many of the tools.

My feeling is if a new tool popped up and had an access profile very much like one of the lower volume OTAs, it would allow the tool to operate without drawing undue interest from the carriers.