While not a direct part of the Runnable API, Atmo does include a method of providing authentication for HTTP and GraphQL made by the Runnable API. Atmo helps with authenticating these requests by injecting the Authorization header to your Runnable's requests based on the configuration in your Directive. For example:

headerType: bearer
value: env(GITHUB_TOKEN)

This uses the env keyword to augment any request (either HTTP or GraphQL) to the domain with an Authorization header containing the value bearer {GITHUB_TOKEN}, with the environment variable evaluated at runtime. The value can be a static string if needed, but the env keyword is more common as it allows your application to be configured in different environments.

This strategy of authentication injection allows Atmo to handle sensitive values without ever giving the code inside the Runnable sandbox access to them. This is an important aspect of Atmo's security model, and helps maintain healthy security practices.