So far the most usage pattern that makes since is to just query the DHT (or a relay if you are in a browser env) and parse the packet yourself. Which what Pkarr client does

That means you have to then take the parsed info and pass it to your HTTP client after manually changing the URL.

That is the most secure way as well since you get to verify the signature yourself, which won't be available if you query a DNS server that supports Pkarr.

Ideally, browsers (and Curl) will eventually have embedded Pkarr client, but we are far from that.

We are also working on ways that makes Pkarr useful in TLS, and if that bans out we will try to lobby anyone who listens to support that.

So who knows, maybe eventually browsers not only will resolve Pkarr urls, but show a green lock too.