Integration of AI providers via API keys
To use the AI function in preeco | datenschutz, an API key from a supported provider such as OpenAI, Anthropic, or Langdock is required. An existing web subscription to an AI service typically does not include API access, as these are two separate products. The API key is stored under "Settings > Integrations", and usage-based costs may apply for each request sent to the respective provider.
If you want to use the AI function in preeco | datenschutz, you need an API key from a supported AI provider. It is important to understand that a subscription to the web interface of an AI service does not automatically include API access.
Supported AI providers
preeco | datenschutz supports the integration of the following AI providers via an API interface, among others: OpenAI, Anthropic, Langdock, Mistral, and Google Gemini.
To use the AI function, you must store the API key of the desired provider under "Settings > Integrations".
The difference between web subscription and API access
Many users already have a paid subscription with an AI provider and assume that they can also use an API key with it. In most cases, however, this is not possible, as these are two separate products.
A web subscription allows 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 | datenschutz – to connect to the provider's AI services.
What does this mean for using preeco | datenschutz?
Before storing an API key in preeco | datenschutz, 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 usage. You typically need 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-powered request sent from preeco | datenschutz to the respective provider, costs may be incurred on the API provider's side if 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.