Thanks for looking into it (and for signing up)! I’m glad to make any changes on this end, especially since key support is brand new (so there’s a lot of flexibility in adjusting API endpoint output at this stage).
When people load a PGP key, I’m storing both the short fingerprint and the WKD hash. I could store the full fingerprint if that’s easier, no problem. (Honestly, I only chose the short one because it’s what I’m used to seeing from Keybase.)
I’ve just updated the /address/info endpoint to show all keys. It now provides them in an array by key type, with an array of all fingerprints/keys for each type. So now multiple keys are easily supported. It still provides the short fingerprint for PGP keys, and the full key for all other key types. This probably isn’t ideal, as it’s not really consistent, so if you have any thoughts or preferences on what might work better (for Keyoxide or in general) I’m all ears.
As for the /address/web endpoint, I’ve just added a response for unauthenticated requests that will provide the HTML output.
Thanks again for your support, and let me know if you have any questions or suggestions about anything. Glad to do whatever’s needed to make things easy!