
That's the least of their worries. We've tried something similar in the recent past, and the model had such a high error rate (generating either syntactically or semantically inaccurate queries) that it never really got anywhere. All language model outputs currently require human validation. Any service that tries to do otherwise is... premature at best.