> For the complete documentation index, see [llms.txt](https://docs.gocontent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gocontent.ai/gocontent-social-posts/edit-and-manage-my-posts./sources.md).
# Sources
Having access to sources allows for improvement in:
* **Credibility and reliability:** Displaying the source allows for verifying the origin of the information and ensuring its reliability.
* **Transparency:** By citing sources, it clearly shows where the information comes from and how it was obtained.
* **Facilitation of research:** For those who wish to delve deeper into the topic, sources provide useful starting points for further research and exploration.
### **How to access the sources?**
Access the sources of your post by clicking on '**Sources**' at the bottom left of your post.
You can access the main source from which your post was generated.
---
# 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.gocontent.ai/gocontent-social-posts/edit-and-manage-my-posts./sources.md?ask=&goal=
```
`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.