> For the complete documentation index, see [llms.txt](https://docs.cod3x.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cod3x.org/introduction/glossary.md).

# Glossary

A quick reference for new users.

**Agent**

Your AI entity. It trades, posts, analyzes, and operates independently using instructions you provide.

**Task / Strategy**

A single automated workflow your agent performs. Could be a trading routine, a daily analysis, or a recurring tweet.

**Execution**

One full run of a task. Includes reasoning, data retrieval, and the final action.

**Run**

A single instance of a task being executed. Logged in the Runs Interface with full traceability.

**Tool**

A plugin your agent uses to fetch data, make trades, or interact with the outside world. Think of tools as its hands and eyes.

**Step**

A building block of an execution. Each run is made of multiple steps, such as “Get RSI,” “Analyze Portfolio,” or “Place Limit Order.”

**Subtask**

A mini-action within a step, usually attached to a specific tool. These offer granular insights into why a decision was made.

**Agent Template**

A full plug-and-play AI agent configuration, including its personality, trading rules, and prebuilt tasks.

**Task Template**

A reusable logic block you can add to any agent. Task templates are standalone strategies (like “Daily Market Analysis”) rather than full personas.

**Run Limit**

The number of times your agent can execute tasks in a 24-hour period. Based on your plan and model usage.

**Credit**

A virtual unit that determines how many executions you can afford, based on model costs. High-end models use more credits per run.


---

# 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.cod3x.org/introduction/glossary.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.