> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/integrations/builtin/credentials/cohere.md).

# Set up Cohere credentials in Duaer

Store Cohere connection details in Duaer for digital-organization nodes to use at runtime. Secrets are protected by the instance encryption key and are not written into node parameters.
## Get a Cohere API key <a href="#get-an-api-key" id="get-an-api-key"></a>

The Duaer Cohere API credential needs one API key:

1. Sign in to [the Cohere Dashboard](https://dashboard.cohere.com/api-keys).
2. Open API Keys and create a Trial or Production key. Copy the key right away; it is usually shown only once.
3. In Duaer, create a Cohere API credential, paste the key into API Key, and save. Duaer tests the connection with it.

Trial keys are free but rate-limited, so use them only to try things out. Before the digital organization runs for real, add billing in Cohere and switch to a Production key. The same key serves Cohere Chat Model, Embeddings Cohere, and Reranker Cohere.

## Cohere API fields in Duaer <a href="#cohere-api" id="cohere-api"></a>

In Duaer, choose Cohere API when you create a credential, then fill in these fields:

- API Key (required, secret)

When you save, Duaer tests the connection with these values.

Duaer nodes that use it: [Embeddings Cohere](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.embeddingscohere.md), [Cohere Chat Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmchatcohere.md), [Cohere Model](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.lmcohere.md), [Reranker Cohere](/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.rerankercohere.md).

## Save the connection in Duaer

Open Credentials and create Cohere. Fill in the key, OAuth, or server fields. After you save, digital-organization nodes reference this credential instead of putting the secret in a parameter.

Credential values are protected by the instance encryption key. If you change or lose that key, stored credentials cannot be decrypted. See the hosting notes on encryption keys. 

## Who can use this credential

Who can see or edit it follows projects and roles. Do not paste secrets into chat or variables. External vaults are covered under external secrets.
## Questions

### Do Cohere secret values appear in Duaer node parameters?

No. In Duaer, Cohere secrets stay in the credential. Nodes only reference the credential. Execution records should not show the plaintext secret either.

### What usually stops a Cohere credential from saving in Duaer?

Wrong fields, an OAuth callback that does not match the instance URL, or a role that cannot create credentials. Check the fields Cohere expects, then confirm you can create credentials in that project.