> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/t4i/commands-overview/ilogic-samples.md).

# iLogic Samples

The various iLogic commands available in the "iLogic Samples" panel of the Be.Smart T4I ribbon are sample iLogic commands provided in the Be.Smart Tools4Inventor installation file. They can be accessed/set/deleted using the iLogic command editor.

{% hint style="info" %}
Since commands in this section are provided as sample iLogic commands that are added to the ribbon using the [iLogic commands](/t4i/commands-overview/be.smart-t4i/ilogic-commands.md) window, their names on the ribbon are not translated by default. If needed, users can change the command button *Display names* in that iLogic commands editor window.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.besmart.software/t4i/commands-overview/ilogic-samples.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 `build a script that syncs our docs to a CMS` 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.