Skip to main content
Managed tools use credentials fetchbean supplies. The providers below act on your account, so you connect them once and fetchbean stores the credential encrypted. After that you call their tools with your fetchbean key like any other tool. Connect and revoke from the dashboard. See the Connections guide for the full walkthrough.

​
Paste a key

These providers connect with a key generated in the provider’s own dashboard. Fields marked ? are optional.

​
Connect with OAuth

These providers connect through a redirect. Authorize fetchbean in the provider’s own consent screen, then start the flow from the dashboard or with GET /v1/connections/{provider}/oauth/start.

​
Agent subscriptions

Agent subscriptions authorize an agent runtime rather than a provider API. Their credential documents are stored as encrypted secrets. Provider API keys and OAuth tokens are not returned by the connections API. Agent subscription credentials can be retrieved with GET /v1/connections/{provider}/credential and updated with POST /v1/connections/{provider}/credential using an org API key, so unattended runners can use and refresh them. These routes only work for an existing agent-subscription connection. For Codex, choose or drop auth.json in the dashboard. If Codex uses the system keyring and no file exists, the connect dialog provides a one-time file-storage login command. Use a ChatGPT sign-in, not an API-key login. Manual paste remains available as a fallback. For Claude Code, run claude setup-token on your own machine and paste the token it prints. Storage is enabled; hosted execution is not.