@abbe98 Updating here in order to 'close the loop' and notify anyone else following this thread - a response to this phabricator ticket was posted today by the project's engineering manager https://phabricator.wikimedia.org/T365690#9864001

@abbe98 noted. I've pinged the team.

@abbe98 Now that the Enterprise API suite is more than merely 'feature parity' with existing APIs, we are in the 'good problem to have' place of more people wanting to use them for more things. Originally it was set up in a completely different place, in a completely different website, in order to NOT impinge/conflict with existing APIs. So now (as mentioned above), with greater demand, we're going to try to lower the barrier to entry and be more consistent with the pre-existing services.

@abbe98 there are no exclusive content no exclusive contracts. As per https://meta.wikimedia.org/wiki/Wikimedia_Enterprise/Principles
The $ comes from the speed and volume of throughput, the SLA guaranteeing stability/uptime/response time, and the ‘hold my hand’ customer service. These are all ‘additional’ things that do not encroach on the freedom [in the technical definition of the word] of Wikimedia content or the movement.

@abbe98 could you describe the technical access you‘d like - but cureently can’t achieve - either on meta talkpage, or in a phabricator ticket [or email or via the api website if you prefer]? I can ensure that someone from the engineering side of the project responds.

@abbe98
Are you saying the no-cost access via WMCS and/or via the API's website "doesn't work" in a literal sense (broken) or is inadequate (intellectually)?
Are you saying the documentation here https://enterprise.wikimedia.com/docs/ is insufficiently detailed? what would you like more detail about?
So far we've not had any community user express any specific use case that they've been unable to fulfil. Please bring any specifics to the talkpage (or phabricator).