> For the complete documentation index, see [llms.txt](https://energytransition.gitbook.io/esdl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://energytransition.gitbook.io/esdl/esdl-concepts/data-types/energy-system-information/carriers.md).
# Carriers
ESDL allows you to describe a list of carriers with parameters that are used inside your model
There are two types of carriers:
* Commodities
* Energy carriers
They serve different purposes but can be combined in the same model if required. Choices depend on the scope of the model.
The `Carriers` class is a collection of the abstract class `Carrier`. The `Carrier` class can have the following parameters:
* an `id` paramater that is used for referring to carriers.
* a `name` parameter to describe the name of the carrier.
* a `cost` paramater of type GenericProfile (allows both a fixed value as a profile that changes over time).
* a `dataSource` parameter to document the origin of the information you're using
The `Commodity` and `EnergyCarrier` classes are subclasses of `Carrier`.
## Commodity
The `Commodity` class is an abstract class, with the following subclasses:
* ElectricityCommodity: can be used for electricity. If required a distinction between different voltage levels can be made (LV, MV, HV, ...). A `voltage` parameter can be specified.
* GasCommodity: can be used for natural gas, biogas, carbon dioxide (CO2), hydrogen (H2), and so on. Distinction is done based on the `name` parameter.
* HeatCommodity: can be used for heat. If required a distinction between different temperature levels can be made (LT, MT, HT, ...). A `temperature` parameter can be specified.
* EnergyCommodity: can be used for describing energy balances (expressed in Joules, independent of the specific commodity).
## EnergyCarrier
The `EnergyCarrier` class has the following parameters:
* an `energyContent` parameter: allows the specification of the energy content of the energy carrier
* an `energyContentUnit` parameter: the unit of the `energyContent` paramater
* an `emission` parameter: allows the specification of emission values per energy content
* an `emissionUnit` parameter: the unit of the `emission` parameter
* an `energyCarrierType` parameter: an enumeration with options `UNDEFINED`, `RENEWABLE`, `FOSSIL`
* a `stateOfMatter` parameter: an enumeration with options `UNDEFINED`, `SOLID`, `LIQUID`, `GASEOUS`
This class is based on the [list of energy carriers](https://www.rvo.nl/sites/default/files/2018/03/Nederlandse%20energiedragerlijst%202018.pdf) as published by RVO:
An example ESDL file with this information looks like:
```markup
```
---
# 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://energytransition.gitbook.io/esdl/esdl-concepts/data-types/energy-system-information/carriers.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.