Hahaha… pretty much yes. But instead of defining yet another API, model providers agree to one popular standard and adapt or write a wrapper so that their models can support that popular standard too, if not fully embrace the whole standard.

Their API specs is one thing. Standardizing their API is another. The industry should arrive at a consensus on how the inputs and outputs for all models should look like. Like the Swagger / OpenAPI spec for REST APIs.