Recently found out there's a way to bypass a need for API usage in this: some madlad bulk uploads all the data on E6 tags in .csv format DAYLY. Bruh, daily. Whoever you are, you're a hero. Sooooo, now that I'm able to access implied and tag list offline in a very convenient table, next question is, so what now?

Overall my goal is to create a GUI that would allow a person uploading see lots of categories from wiki and add them to the main typing field for the tags in one click

Currently thinking of this for an overall structure:
GUI buttons and expandable fields come straight from wiki
might come up with a way to autostrip dis boi (if someone updates wikis)
tag bases can be accessed in csv file offline (after purging the bloat)
same for tag implications

future ideas for GUI:

download wiki pages in html
create a scrip that would strip them down, leaving:
categories that expand
subcategories

they would go on to later become clickable and easily addable to the main field

I'd say some work needs to be done to implications. Right now E6 inputs tags, implied by what you've typed. which is great, that's what we want to happen. But what if there was an easy way to peep what the tag you typed might imply, so you can see what you might be missing?

e.g.:
I type anal
it shows:
anal fingering, anal penetration, anal insertion, anal orgasm....

Might be useful for some instances

Still having trouble visualizing GUI, but I think it'll come to me
Might make it a browser extension for ease of use
Having trouble thinking of a convenient way to get all the benefits of E6 autocomplete tag fields

Fun fact for the day:
After I got rid of the bloat in the tags (tagcount < 30) it yeeted like, 1.5m of them, leaving me with 80k
Much more manageable