LLM Connector (Repository Option) - Revision history

Dgreenwood: /* LLM-enabled features */

2026-03-18T21:05:43Z

LLM-enabled features

@@ Line 21: / Line 21: @@
 After an LLM Connector has been added to the Grooper Root, several LLM-enabled features are available in Grooper. This includes:
+{{#lst:Grooper and AI|llm-constructs}}
 ==LLM connection options ==

Dgreenwood: /* About */

2026-03-18T21:03:04Z

About

← Older revision		Revision as of 16:03, 18 March 2026
Line 15:		Line 15:
	**<li class="fyi-bullet"> Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.		**<li class="fyi-bullet"> Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.
	* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).		* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).
	* '''GCS''' - GCS (Grooper Cloud Services) is a prototype ~~services~~ for LLMs offered by and through Grooper directly.		* '''GCS''' - GCS (Grooper Cloud Services) is a prototype service for LLMs offered by and through Grooper directly.
	**<li class="attn-bullet">''This provider is still under development. Users may ignore this provider at this time.''		**<li class="attn-bullet">''This provider is still under development. Users may ignore this provider at this time.''

Dgreenwood at 21:02, 18 March 2026

2026-03-18T21:02:12Z

← Older revision		Revision as of 16:02, 18 March 2026
Line 16:		Line 16:
	* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).		* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).
	* '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly.		* '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly.
	**<li class="attn-bullet">''This provider is still under development. ~~Most users~~ may ignore this provider at this time.''		**<li class="attn-bullet">''This provider is still under development. Users may ignore this provider at this time.''

	== LLM-enabled features ==		== LLM-enabled features ==

Dgreenwood: /* About */

2025-11-13T15:42:49Z

About

@@ Line 17: / Line 17: @@
 * '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly.
 **<li class="attn-bullet">''This provider is still under development. Most users may ignore this provider at this time.''
 ==LLM connection options ==

Dgreenwood: /* OpenAI compatible services */

2025-09-29T18:54:41Z

OpenAI compatible services

← Older revision		Revision as of 13:54, 29 September 2025
Line 43:		Line 43:
	==== OpenAI compatible services ====		==== OpenAI compatible services ====

	Grooper can connect to any LLM service that adheres to the OpenAI API standard using the "OpenAI" provider. Compatible APIs must use "chat/completions" and "embeddings" endpoints ~~similar to~~ OpenAI API to interoperate with Grooper's LLM features.		Grooper can connect to any LLM service that adheres to the OpenAI API standard using the "OpenAI" provider. Compatible APIs must use "chat/completions" and "embeddings" endpoints like OpenAI API to interoperate with Grooper's LLM features.

	We have confirmed the following services will integrate using the OpenAI provider:		We have confirmed the following services will integrate using the OpenAI provider:

Dgreenwood: /* LLM connection options */

2025-09-24T14:04:58Z

LLM connection options

← Older revision		Revision as of 09:04, 24 September 2025
Line 19:		Line 19:

	==LLM connection options ==		==LLM connection options ==
			<section begin="LLM connection options" />
	While there are two primary LLM Providers (OpenAI and Azure), there are several different providers and model types you can connect Grooper to using just these two providers.		While there are two primary LLM Providers (OpenAI and Azure), there are several different providers and model types you can connect Grooper to using just these two providers.

	=== OpenAI API ===		==== OpenAI API ====

	Grooper's LLM based features were primarily designed around OpenAI's models. The Grooper development team uses OpenAI models internally using the OpenAI API. Connecting to the OpenAI API is regarded as the "standard" way connecting Grooper to LLMs.		Grooper's LLM based features were primarily designed around OpenAI's models. The Grooper development team uses OpenAI models internally using the OpenAI API. Connecting to the OpenAI API is regarded as the "standard" way connecting Grooper to LLMs.
Line 41:		Line 41:
	# Press "OK" buttons in each editor to confirm changes and press "Save" on the Grooper Root.		# Press "OK" buttons in each editor to confirm changes and press "Save" on the Grooper Root.

	=== OpenAI compatible services ===		==== OpenAI compatible services ====

	Grooper can connect to any LLM service that adheres to the OpenAI API standard using the "OpenAI" provider. Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.		Grooper can connect to any LLM service that adheres to the OpenAI API standard using the "OpenAI" provider. Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.
Line 71:		Line 71:
	# Press "OK" buttons in each editor to confirm changes and press "Save" on the Grooper Root.		# Press "OK" buttons in each editor to confirm changes and press "Save" on the Grooper Root.

	=== Azure AI Foundry deployments ===		==== Azure AI Foundry deployments ====

	Grooper connects to Microsoft Azure OpenAI models and Azure AI Foundry (formerly Azure AI Studio) model deployments by adding an "Azure" provider to an LLM Connector. Each model must be deployed in Azure before Grooper can connect to it.		Grooper connects to Microsoft Azure OpenAI models and Azure AI Foundry (formerly Azure AI Studio) model deployments by adding an "Azure" provider to an LLM Connector. Each model must be deployed in Azure before Grooper can connect to it.
Line 116:		Line 116:
	#:*<li class="fyi-bullet"> When enabled, certain instructions Grooper generates and information handed to a model are sent as "system" messages instead of "user" messages. This helps an LLM distinguish between contextual information and input from a user. This is recommended for most OpenAI models, but may not be supported by all compatible services.		#:*<li class="fyi-bullet"> When enabled, certain instructions Grooper generates and information handed to a model are sent as "system" messages instead of "user" messages. This helps an LLM distinguish between contextual information and input from a user. This is recommended for most OpenAI models, but may not be supported by all compatible services.
	# Press "OK" buttons in each editor to confirm changes and press "Save" on the Grooper Root.		# Press "OK" buttons in each editor to confirm changes and press "Save" on the Grooper Root.
			<section end="LLM connection options" />

Dgreenwood: /* OpenAI compatible services */

2025-07-15T22:11:25Z

OpenAI compatible services

← Older revision		Revision as of 17:11, 15 July 2025
Line 66:		Line 66:
	#* ''Bearer'' - Choose this option if the API uses a bearer token to authorize web calls (Example: OpenAI API and Groq use the bearer method).		#* ''Bearer'' - Choose this option if the API uses a bearer token to authorize web calls (Example: OpenAI API and Groq use the bearer method).
	#* ''APIKey'' - Choose this option if the API uses an API key to authorize web calls (Example: Nvidia's NIM API uses the key method).		#* ''APIKey'' - Choose this option if the API uses an API key to authorize web calls (Example: Nvidia's NIM API uses the key method).
	# In the "API Key" property, enter API key.		# In the "API Key" property, enter the API's key.
	# (Recommended) Turn on "Use System Messages" (change the property to "True").		# (Recommended) Turn on "Use System Messages" (change the property to "True").
	#:*<li class="fyi-bullet"> When enabled, certain instructions Grooper generates and information handed to a model are sent as "system" messages instead of "user" messages. This helps an LLM distinguish between contextual information and input from a user. This is recommended for most OpenAI models, but may not be supported by all compatible services.		#:*<li class="fyi-bullet"> When enabled, certain instructions Grooper generates and information handed to a model are sent as "system" messages instead of "user" messages. This helps an LLM distinguish between contextual information and input from a user. This is recommended for most OpenAI models, but may not be supported by all compatible services.

Dgreenwood: /* OpenAI API */

2025-07-15T22:10:49Z

OpenAI API

← Older revision		Revision as of 17:10, 15 July 2025
Line 36:		Line 36:
	# Add the "OpenAI" option.		# Add the "OpenAI" option.
	# In the "API Key" property, enter your OpenAI API Key.		# In the "API Key" property, enter your OpenAI API Key.
	#:*<li class="fyi-bullet"> ~~Technically OpenAI's "API keys" are bearer tokens.~~ You '''''do not''''' need to adjust the "Authorization" property. It should be "Bearer".		#:*<li class="fyi-bullet"> You '''''do not''''' need to adjust the "Authorization" property. It should be "Bearer". The OpenAI API uses bearer tokens to authenticate API calls.
	# (Recommended) Turn on "Use System Messages" (change the property to "True).		# (Recommended) Turn on "Use System Messages" (change the property to "True).
	#:*<li class="fyi-bullet"> When enabled, certain instructions Grooper generates and information handed to a model are sent as "system" messages instead of "user" messages. This helps an LLM distinguish between contextual information and input from a user. This is recommended for most OpenAI models, but may not be supported by all compatible services.		#:*<li class="fyi-bullet"> When enabled, certain instructions Grooper generates and information handed to a model are sent as "system" messages instead of "user" messages. This helps an LLM distinguish between contextual information and input from a user. This is recommended for most OpenAI models, but may not be supported by all compatible services.

Dgreenwood: /* About */

2025-07-15T21:43:55Z

About

← Older revision		Revision as of 16:43, 15 July 2025
Line 13:		Line 13:
	There are currently 3 "LLM Provider" options:		There are currently 3 "LLM Provider" options:
	* '''OpenAI''' - This provider connects Grooper to LLMs offered by the OpenAI API or compatible APIs.		* '''OpenAI''' - This provider connects Grooper to LLMs offered by the OpenAI API or compatible APIs.
	:<li class="fyi-bullet"> Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.		**<li class="fyi-bullet"> Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.
	* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).		* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).
	* '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly.		* '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly.

Dgreenwood: /* About */

2025-07-15T21:43:29Z

About

← Older revision		Revision as of 16:43, 15 July 2025
Line 15:		Line 15:
	:<li class="fyi-bullet"> Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.		:<li class="fyi-bullet"> Compatible APIs must use "chat/completions" and "embeddings" endpoints similar to OpenAI API to interoperate with Grooper's LLM features.
	* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).		* '''Azure''' - This provider connects Grooper to LLMs offered by Microsoft Azure in their "Model Catalog" (including Azure OpenAI models).
	* '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly. ''This provider is still under development. Most users may ignore this provider at this time.''		* '''GCS''' - GCS (Grooper Cloud Services) is a prototype services for LLMs offered by and through Grooper directly.
			**<li class="attn-bullet">''This provider is still under development. Most users may ignore this provider at this time.''

	==LLM connection options ==		==LLM connection options ==