> For the complete documentation index, see [llms.txt](https://docs.mobiusflow.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mobiusflow.com/help/mobiusflow-v3/mobiusflow-toolbox-v3/objects.md).
# Objects
What are MobiusFlow objects and how are they used?
MobiusFlow Objects represent real or virtual devices such as sensors, rooms, pieces of equipment, and machinery. All objects are based on an [Object Profile](/help/mobiusflow-v3/mobiusflow-toolbox-v3/object-profiles.md) which describes the shape of the object i.e. what properties (resources) an objects has, the data type of each property (resource), and metadata describing the object and it properties.
{% hint style="info" %}
MobiusFlow object properties are called resources. A resource holds a single value associated with an object.
E.g. an air quality sensor object may have separate resources for temperature, humidity, and CO2 level.
{% endhint %}
For more information on objects and resources read the [MobiusFlow Architecture](/help/mobiusflow-v3/mobiusflow-overview/mobiusflow-architecture.md) article.
Objects must belong to a [service](/help/mobiusflow-v3/mobiusflow-engine-api-v3/services.md). To add new objects or configure existing objects on a service open the Service's Objects page by clicking on the service in the main menu or clicking on the main body of a service's card on the Services page.
---
# 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.mobiusflow.com/help/mobiusflow-v3/mobiusflow-toolbox-v3/objects.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.
