Could we make acoderd.API struct that contains this? Similar to how the AGPLcoderd package is structured.

the public keys are baked in at the package level this way. Isn't this what we want?

It might make it easier to do integration testing if we could inject the keys in ascoderd.Options on creation of the API, so that tests could generate their own keys and then use them, but I worry that sort of machinery would be tempting for end users looking to bypass our licensing. Granted, right now they can just modify thekeys/2022-08-12 file, but each layer we bubble this up through makes it that much more obvious how to get away with it.

It seems like this test doesn't have to be internal.

it modifies thekeys variable in-place during the tests (patch paradigm). I want to keep that variable unexported, so the tests need to be internal.