> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/6.0/v4.5/component-definition/manifest/authconfig.md).

# authConfig

This section specifies which service should be used to search for additional configuration values.

```
{
	"authConfig": {
		"service": "appmixer:deepai"
	}
}
```

To set additional global values for a service, use the authConfig API. See the [Service Configuration](/6.0/v4.5/api/service-configuration.md) section for more information. The purpose of this property is to offer authentication settings for components/services that do not require user authentication. Consider that [*deepai*](/6.0/v4.5/app-registration/deepai.md) service. It is a service that requires authentication (API key), but you don't want your users to provide their API keys for it. You want to use your API key for all your users. You cannot use define the [*auth*](/6.0/v4.5/component-definition/manifest/auth.md) property in component.json, because that would tell Appmixer to show *Connect Account* button to users in the frontend.

This is not needed since version 4.2. Appmixer will look for service configuration for each component without `auth` section. More details in [here](/6.0/v4.5/component-definition/configuration.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/6.0/v4.5/component-definition/manifest/authconfig.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.