Interesting — how does the agent authenticate to paid/protected endpoints? This is the piece most agent UX tools skip. HTTP 402 + macaroon tokens handle this natively without API keys.
Currently you can simply add a username/password to log in with under "+ Instructions" or log in yourself and paste in a JSON exported from the Cookie-Editor browser extension under "+ Cookies".
I'll look into HTTP 402 + macaroon tokens, thanks!