Integrating AI providers via API keys
To use the AI feature in preeco | data protection, you need an API key from a supported provider such as OpenAI, Anthropic or Langdock. An existing web subscription with an AI service usually does not include API access, as these are two separate products. The API key is stored under „Settings > Integrations", whereby usage-based costs may be incurred with the respective provider for each request.
If you want to use the AI feature in preeco | data protection, you need an API key from a supported AI provider. It is important to understand that a subscription for the web interface of an AI service does not automatically include API access.
Supported AI providers
preeco | data protection supports, among others, the connection of the following AI providers via an API interface: OpenAI, Anthropic, Langdock, Mistral and Google Gemini.
To be able to use the AI feature, you must store the API key of the desired provider under "Settings > Integrations".
The difference between a web subscription and API access
Many users already have a paid subscription with an AI provider and assume that they can use an API key with it as well. In most cases, however, this is not possible, as these are two separate products.
A web subscription enables the use of the respective provider's user interface, for example the chat function of ChatGPT or Claude. API access, on the other hand, enables external software – such as preeco | data protection – to be connected to the provider's AI services.
What does this mean for use in preeco | data protection?
Before you store an API key in preeco | data protection, check whether you already have API access with one of the supported providers. An existing web subscription, such as ChatGPT Plus or Claude Pro, does not entitle you to API use. You usually have to register separately for API access and top up credit. With Langdock, API access may already be included depending on the chosen subscription.
For each AI-supported request sent via preeco | data protection to the respective provider, costs may be incurred on the side of the API provider, provided a usage-based billing model is used.
Changes and errors may occur. The information in this article has been carefully compiled, but does not claim to be complete or correct.