> For the complete documentation index, see [llms.txt](https://help.roolz.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.roolz.net/en/company-directory/all-you-need-to-know/the-information-displayed-in-the-profile.md).
# The information displayed in the profile
**Company profile** is a "business card" of your company on Roolz. A well-filled profile allows you to advertise your business for free in the companies directory (it will be placed higher in the list and will be more visible), where shippers often look for new carriers and forwarders.
In the directory, company information is briefly presented with a profile card where you can fill in the following fields:
* Company name;
* Logo;
* Motto;
* Company role;
* Public offers amount;
* Fleet size (for carriers);
* Company size.
Once you click on the card, [the company profile](/en/companies/company-profile.md) will open.
---
# 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://help.roolz.net/en/company-directory/all-you-need-to-know/the-information-displayed-in-the-profile.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.