@Abbe98 thanks for the explicit ask on the code snippet scenario it clarifies the asks for me. I was under the impression this was something that could be done server side. In the case of the client side only scripts, the solution would not be simple to implement. Some possibilities are listed below (I understand that some of these might be options that can not be used or are ill advised for some use cases):
Ask the user of the javascript to authenticate via username and password. That way you are facilitating the use of APIs but the procurement of the credentials is left to the end user. (Then follow best practices for storing and managing api keys client side for the session)
Use a proxy. The WMCS provides authentication free access to Enterprise APIs. Having code running there that ferries the requests over is a possibility.
Have a server side auth management implemented that allows for client side calls to be made. This would be more complicated than the proxy mentioned in 2. But could allow for a longer running instance which might be limited on WMCS (Authenticate and obtain a JWT: Typically done on the server-side. You send user credentials to your server, and the server returns a JWT.)

Hello @Abbe98. Sorry for the delay. Thank you for your patience in waiting for my reply. I’m posting a reply here in Phabricator (and @LWyatt will link to it on the Mastodon thread where this question originated). But moreover, given the question you have asked might come up again in the future, we will add “why does the API require authentication?” to our FAQ on metawiki soon.

@Abbe98 Let me look into your requests. I will get back to you in a few days.
In the meantime, a request which I think is similar to yours was previously posted on our talk page back in January. Please check if my response there addresses any of your questions/concerns:
https://meta.wikimedia.org/wiki/Talk:Wikimedia_Enterprise#c-HShaikh_(WMF)-20240112213100-LWyatt_(WMF)-20240104000900

I believe this has been solved. A delivery mechanism has been setup for Francisco and Ehi has all the access she needs

Would it be possbile to block signups from offending lists as part of the pre-signup lambda

@Mitar Preferably we would like it if you can signup and use the trial account to see if that meets your needs. But as mentioned earlier access to our APIs are also available through the WMCS services.
Following the Enterprise section on https://wikitech.wikimedia.org/wiki/Portal:Data_Services You can follow the link for PAWS to access the services and create a Jupyter lab instance to access the WME services.

@Kelson pinging to see if this is still on the radar.

yes this is resolved now.

@MPhamWMF Can you confirm that you have credentials now?

Also adding the request to add Ehi to the aws and gitlab access.

We discussed some options and will research a few more on the AWS implementation side and come back early next week.

Sorry I thought I had already responded but it seems I forgot to hit submit
on the ticket. Reuven is correct we are fine with the current explanation
of something comes up and we n Ed to reopen I will let you know

@DAbad I think we can close this ticket. I was able to get initial results for myself. But if this is something that is going to be revistied by the Data teams. We can keep it around

Sample query:
SELECT * from mediawiki_api_request where year = 2023 and month = 01 and day = 27 and hour = 16 limit 10;

Approving this request for Prabhat. He needs this access to get data analysis done for our team

@elukey thanks for reaching out. @prabhat would be a good resource to talk to regarding any migrations related to moving from ores model. and how deeply Ores is integrated into our systems.