The current implementation fetches the keys from the crawler public directory. This is rather inefficient, and may pose concern as the signer may not have access to internet. My impression is the library could be split as is: * BotAuth class would take only one key * There would be a different class to format the directory as JSON, and generate the [HTTP signature on the directory response](https://datatracker.ietf.org/doc/html/draft-meunier-http-message-signatures-directory-01#name-binding-keys-to-the-directo)