> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/agents-in-the-workspace/sources-and-citations.md).

# Sources and citations

The research references the agent saves and cites as it works.

As the agent researches, it saves the **sources** it uses, such as papers, articles and datasets, so its findings can be traced back to where they came from.

## Where sources come from

Sources are gathered mainly by Evolve Mode's [research specialist](/zerve-docs/agents-in-the-workspace/evolve-mode/specialists.md#research), which searches the web and academic literature and builds a library of citable references. The agent may also save sources it finds while working on other parts of a task.

## Finding sources

Open the **Sources** view in a notebook or thread to see every source the agent has saved.

## Citations

The agent cites its sources:

* **In its replies**, when an answer draws on research
* **In** [**Learnings**](/zerve-docs/agents-in-the-workspace/learnings.md), when a finding or assumption comes from a source
* **In documents it writes**, such as reports drafted by the drafting specialist

{% hint style="info" %}
Check sources before relying on a finding for an important decision. The agent saves where each finding came from so you can do exactly that.
{% endhint %}


---

# 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.zerve.ai/zerve-docs/agents-in-the-workspace/sources-and-citations.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.