> For the complete documentation index, see [llms.txt](https://docs.documint.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.documint.me/templates/working-with-dynamic-data/functions-and-operators/functions/usdvar.md).
# $var
Creates a custom variable in your template which you can access from other parts of your template
{% hint style="info" %}
**Note:**
Variables must be added to templates before (higher up in the template) they are used.
Examples
**Good:**\
`{{$var "tax_rate" 0.07}}` //Variable is declared before it is used
`Tax Rate: {{$number tax_rate "0%"}}`
**Bad:**
`Tax Rate: {{$number tax_rate "0%"}}`
`{{$var "tax_rate" 0.07}}` //Variable is declared after it is used
{% endhint %}
#### Signature
`{{$var name value}}`
#### Arguments
Name
Description
Type
Required
name
The name of the variable. This will be used to access it later. Must be a valid JavaScript key
String
true
value
The value of the variable
Any
true
#### Returns
This function does not have a return value.
#### **Example #1 - Basic**
{% tabs %}
{% tab title="Template" %}
```
{{$var "custom_var" "Custom value"}}
...
{{custom_var}} // Used somewhere else in the template after the above declaration
```
{% endtab %}
{% tab title="Result" %}
Custom value
{% endtab %}
{% endtabs %}
#### Example #2 - Advanced
{% tabs %}
{% tab title="Template" %}
Create a custom variable and set the value to the results of the filter function where we filter items that have a quantity of 10 or more.
Repeat the section for each item in the custom variable
{% endtab %}
{% tab title="Data" %}
```
{
"items":[
{
"name": "Item #1",
"qty": 5
},
{
"name": "Item #2",
"qty": 10
},
{
"name": "Item #3",
"qty": 15
},
{
"name": "Item #4",
"qty": 20
}
]
}
```
{% endtab %}
{% tab title="Result" %}
{% endtab %}
{% endtabs %}
{% hint style="info" %}
Variables can only be accessed after the point in the template where they are declared.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.documint.me/templates/working-with-dynamic-data/functions-and-operators/functions/usdvar.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.