Credentials and 1Password
Credentials lists provider API accounts and subscription sign-ins for the selected mode. A provider API account stores a credential for OpenAI, Anthropic or another provider. A subscription sign-in stores authentication for a subscription-backed relay. These are separate from Modem admin API keys.
Configure a provider account explains adding and assigning API accounts. Subscriptions explains imports, authentication and relay setup.
Link 1Password
- Create a service account in 1Password’s service-account creation wizard . Select the vaults containing your credentials and grant read access to their items. Save the token when 1Password shows it; it is shown only once.
- In Modem, open 1Password and choose Link.
- Enter a name and the service-account token. Modem verifies that the account can list at least one vault.
- Choose Browse to inspect available vaults and items. In a provider credential field, choose the linked integration and secret reference instead of pasting a raw key.
1Password requires creating a replacement service account to change its vault permissions or access. See its service-account setup guide for account requirements and supported vaults.
A secret reference points to a field, such as op://Development/OpenAI/credential. In the 1Password desktop app, enable its CLI integration, then use the field menu’s Copy Secret Reference action. Names containing unsupported characters require IDs; see 1Password’s reference syntax . Use Modem’s reference picker when available rather than assembling paths from display names.
The integration’s optional private-link setting is navigation metadata. It does not authenticate Modem to 1Password.
Refresh metadata or credentials
Modem stores a resolved copy of a vault-backed credential. Requests use that stored value; browsing an item does not fetch a fresh secret for every AI request.
| Action | What changes |
|---|---|
| Browse or refresh the vault browser | Available vault/item metadata |
| Integration Refresh | Stored values for linked provider accounts and supported payment/authentication credential fields |
| Edit a credential source | The reference used for that particular field |
Inspect the refresh report. One target can fail while others update successfully. A failed target retains its previous value. If a reference changes during refresh, the old result is not written to the new reference. A newer refresh can supersede an earlier one.
Provider validation also applies: replacing a Stripe credential cannot silently switch its connected account or mode, and refreshing a connected Firebase project ID cannot switch its identity. Fix the credential or connection instead of repeatedly refreshing an incompatible value.
Unlink an integration
Before unlinking, replace or remove every credential sourced from the integration. Check provider accounts and project payment/authentication settings. A zero count in Linked accounts does not prove there are no other dependencies.
Modem refuses unlinking while a non-deleted credential depends on the integration. Once unlinking succeeds, its stored service-account token is cleared. This does not revoke the service account in 1Password; manage that account in 1Password separately.
If linking or refreshing fails, verify the token, vault access and field reference. An unavailable 1Password service is different from a rejected token. Keep the request reference from the error when asking for help, and omit the token and resolved key.