> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/knowledge-integrations.md).

# Knowledge Integrations

Knowledge integrations, also referred to as API sources, are configured under EbbotGPT Knowledge in the platform. The knowledge sources, regardless of source type, can be leveraged by AI agents across chat and Automations. 

## Knowledge integrations in Ebbot

EbbotGPT Knowledge allows you to connect to various external systems via API, enabling your AI agents to utilize secure data from sources like intranets or private knowledge bases. By enabling Automatic updates, your AI agent’s knowledge remains synchronized with the source, ensuring that updates made in your primary systems are reflected in Ebbot automatically.

Visit the page below to learn about our knowledge integrations, also referred to as API sources.

{% content-ref url="/pages/pvs2tMpzbAhc1NDreFNu" %}
[API sources](/ebbot-docs/core-capabilities/ebbotgpt/ebbotgpt-knowledge/source-types/api-sources.md)
{% endcontent-ref %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ebbot.ai/ebbot-docs/integrations/knowledge-integrations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.