If you're using AI agents or LLM tool-use, you've probably pasted API keys somewhere you shouldn't or have them in the agent's environment.
I built Wardgate [1] because I wanted agents to access my calendar, tasks, e-mail and other services, but not by giving them my actual credentials or giving them full access.
For some services you can create API keys with limited scope, but most often API keys just get full capabilities.
Wardgate is a proxy: agents call Wardgate endpoints, Wardgate injects real credentials, enforces access rules, and logs everything. The agent never sees your keys.
Written in Go, easy to self-host. Has presets for common services (Todoist, GitHub, Gmail, etc.) and IMAP/SMTP adapters for email.
Happy to discuss the architecture or take feedback.
Comments
If you're using AI agents or LLM tool-use, you've probably pasted API keys somewhere you shouldn't or have them in the agent's environment.
I built Wardgate [1] because I wanted agents to access my calendar, tasks, e-mail and other services, but not by giving them my actual credentials or giving them full access.
For some services you can create API keys with limited scope, but most often API keys just get full capabilities.
Wardgate is a proxy: agents call Wardgate endpoints, Wardgate injects real credentials, enforces access rules, and logs everything. The agent never sees your keys.
Written in Go, easy to self-host. Has presets for common services (Todoist, GitHub, Gmail, etc.) and IMAP/SMTP adapters for email.
Happy to discuss the architecture or take feedback.
[1] https://github.com/wardgate/wardgate