> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/precast-concrete/feature-descriptions/beam-reinforcement/configuration-settings/main-rebar-ends.md).
# Main Rebar - Ends
Options for adding different end shapes of Main rebar:
These options can be used only after Main rebar layout has been defined.
**Row position** and **Rebar bar type** - these columns come from the Layout tab and show all rebar defined there.
Then for selected rebar you can define the ending option:
**End Type**
* **Straight** - simple start/end offsets of main bars will be used as they are defined in the Layout tab.
* **Type 1** and **Type 2** - see pictures and parameters in next columns to define their shape.
**Side** - define at which end of the beam selected rebar shape should be applied
**L1/C1/L2/C2** - defines values for bars ends:
**Rebar start/end hook types** - enable selection of hook types within the project.
---
# 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.besmart.software/3d-modeling-and-design/precast-concrete/feature-descriptions/beam-reinforcement/configuration-settings/main-rebar-ends.md?ask=&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.
