upfront: better use the fdroid client.
/e/ AppLounge goes through its cousin intermediary cleanapk API for fdroid packages (more for historical reasons - it used to channel playstore apks through that API too before going to playstore directly. Have a opinion there but usually threads just derail on that topic).
Now if cleanapk doesn’t catalog more than one arch, you’ll get the one existing - being the arm v7a package - as with all your examples, there wasnt a v8a in the api response (how?)
Couldn’t find an apk with more than one arch to test if the code really can’t pick device arch. It used to if catalogued. I used to look into this.
You can ping at the email address mentioned at https://info.cleanapk.org/ and ask if this is intentionally reduced to v7a or create a gitlab backlog issue, someone will read this.