> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-repository-api/core-api-reference/catalogs/catalog-reference.md).

# Catalog reference

{% hint style="warning" %}
**Navixy Repository API is a work in progress.** This documentation is published for preview purposes only and doesn't reflect a stable release. Structure, field names, and behaviors are subject to change.
{% endhint %}

This page provides a cross-reference of all catalog types organized by their parent entity.

## Device

| Name                                                                                                          | Description                                   |
| ------------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| [DeviceType](/docs/navixy-repository-api/core-api-reference/devices/types.md#type-devicetype)                 | A classification type for devices.            |
| [DeviceStatus](/docs/navixy-repository-api/core-api-reference/devices/types.md#type-devicestatus)             | An operational status for devices.            |
| [DeviceModel](/docs/navixy-repository-api/core-api-reference/devices/types.md#type-devicemodel)               | A specific device model produced by a vendor. |
| [DeviceVendor](/docs/navixy-repository-api/core-api-reference/devices/types.md#type-devicevendor)             | A device manufacturer or vendor.              |
| [DeviceRelationType](/docs/navixy-repository-api/core-api-reference/devices/types.md#type-devicerelationtype) | A type of relationship between two devices.   |

## Asset

| Name                                                                                       | Description                       |
| ------------------------------------------------------------------------------------------ | --------------------------------- |
| [AssetType](/docs/navixy-repository-api/core-api-reference/assets/types.md#type-assettype) | A classification type for assets. |

## Asset group

| Name                                                                                                        | Description                                          |
| ----------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| [AssetGroupType](/docs/navixy-repository-api/core-api-reference/assets/groups/types.md#type-assetgrouptype) | A type for asset groups with membership constraints. |

## Geo object

| Name                                                                                                    | Description                                   |
| ------------------------------------------------------------------------------------------------------- | --------------------------------------------- |
| [GeoObjectType](/docs/navixy-repository-api/core-api-reference/geo-objects/types.md#type-geoobjecttype) | A classification type for geographic objects. |

## Access

| Name                                                                                                           | Description                                                      |
| -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| [Role](/docs/navixy-repository-api/core-api-reference/access-control/types.md#type-role)                       | A role that can be assigned to actors to grant permissions.      |
| [PermissionScope](/docs/navixy-repository-api/core-api-reference/access-control/types.md#type-permissionscope) | A definition of a permission scope that can be granted to roles. |

## Other

| Name                                                                                            | Description                                                              |
| ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| [Tag](/docs/navixy-repository-api/core-api-reference/catalogs/tags.md#type-tag)                 | A tag for labeling and categorizing entities.                            |
| [Module](/docs/navixy-repository-api/core-api-reference/catalogs/system.md#type-module)         | A system module that groups related functionality and permission scopes. |
| [EntityType](/docs/navixy-repository-api/core-api-reference/catalogs/system.md#type-entitytype) | A definition of an entity type in the system.                            |
| [Country](/docs/navixy-repository-api/core-api-reference/catalogs/system.md#type-country)       | A country reference data item.                                           |


---

# 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://navixy.com/docs/navixy-repository-api/core-api-reference/catalogs/catalog-reference.md?ask=<question>&goal=<endgoal>
```

`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.