---
title: Save And Test Credentials
description: "Most site owners should save keys through **GravityOps -> AI Feed -> Credentials**. ## Save A Key 1. Paste the Anthropic key into **Anthropic API Key** and/or the OpenAI key into **OpenAI API Key**. 2. Select **Save Credentials**. 3. Leave…"
url: "https://brightleafdigital.io/docs/save-and-test-credentials/"
updated: "2026-11-18"
category: GravityOps AI Feed / Setup
---

# Save And Test Credentials

Most site owners should save keys through **GravityOps -> AI Feed -> Credentials**.

## Save A Key

1. Paste the Anthropic key into **Anthropic API Key** and/or the OpenAI key into **OpenAI API Key**.
2. Select **Save Credentials**.
3. Leave a field blank on later saves to keep its existing value.
4. To replace a key, paste the new complete key and save again.

The plugin encrypts keys before storing them in the WordPress database. After saving, it never shows the full key again. Instead, the page shows the source, availability, and a short fingerprint. The fingerprint helps distinguish keys without revealing them.

## Test A Key

Use **Test Anthropic** or **Test OpenAI**. The test runs two steps and shows each result in a **Test results** table:

1. **Connection and key**: a request to the provider's Models endpoint, which is not billed.
2. **Text generation**: one very short request to the provider's recommended text model. This is a real request and uses a few tokens.

The results never include the key or anything the provider sent back. They are built only from the HTTP status of each step.

A restricted provider key may allow generation while denying permission to list models. In that case the first step shows **Check** instead of **Failed**, and the second step tells you whether the key can generate text. For an OpenAI key used only for images, confirm image permission in the OpenAI console; a successful image feed run is the final check.

When both a server-managed key and a WordPress-saved key exist, the test form shows an **API Key** selector:

- **Automatic** tests the key the plugin would normally choose.
- **Server configuration (constant/environment)** tests the server-managed key.
- **Anthropic default** or **OpenAI default** tests the encrypted key saved in WordPress.

When only one usable source exists, the selector is hidden because there is no meaningful choice.

## What Automatic Means

Automatic looks for a provider key in this order:

1. The provider-specific PHP constant.
2. The provider-specific environment variable.
3. An enabled encrypted key saved in WordPress.

If a feed has more than one real source available, its **API Key** setting can deliberately choose one. Otherwise the feed omits that setting and uses Automatic.

## When A Test Fails

Confirm that the key was copied completely, belongs to the correct provider, has not been revoked, and has the required API access. Then check provider billing and account status. If a saved key is reported as unavailable or cannot be decrypted, re-enter it; WordPress security-key or dedicated encryption-key changes can invalidate an older encrypted value.

## Stuck? Ask in GravityOps Help

Search past answers or post your question, tagged "ai-feed".

- [GravityOps AI Feed: a feed did not run on submission](https://brightleafdigital.io/community/gravityops-help/4147/)GravityOps Help - 0 replies - 2 weeks ago
- [GravityOps AI Feed is live: Claude and OpenAI as Gravity Forms feeds](https://brightleafdigital.io/community/announcements/3931/)Announcements - 0 replies - 4 weeks ago

[Ask in GravityOps Help](https://brightleafdigital.io/community/gravityops-help/?gofrm_tag=ai-feed)[Open a support request](https://brightleafdigital.io/support/)

GravityOps Weekly

[This iframe contains the logic required to handle Ajax powered Gravity Forms.](about:blank)
