> For the complete documentation index, see [llms.txt](https://docs.iotex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iotex.io/ioid/technical-specification/device-nft.md).

# Device NFT

Device NFTs are [ERC-721](https://eips.ethereum.org/EIPS/eip-721) tokens that serve as the on-chain representation of physical machines or autonomous agents. They are a core primitive in the ioID architecture, acting as the canonical link between the real world and on-chain identity, ownership, and programmability.

{% hint style="success" %}
In many cases, a **Device NFT** already exists within a DePIN project as part of its native infrastructure, to represent their deployed devices. However, if a Device NFT contract is not already available, it can be created as part of project registration  flow.
{% endhint %}

## Purpose

Each Device NFT functions as a unique digital certificate for a specific machine or AI agent, enabling:

* On-chain registration of new physical assets
* Ownership tracking and transfers
* Access control via smart contracts (e.g., MBAs)
* Integration into reward systems, staking mechanisms, or AI agent networks

## When is a Device NFT Minted?

Device NFTs are typically minted at the moment of asset creation. This may include:

* Manufacturing of a physical device (e.g., an IoT sensor, drone, EV charger)
* Bootstrapping of an AI agent or digital twin
* Provisioning a new node in a decentralized network (DePIN, DeAI)

Minting represents the genesis event that brings the real-world asset representation onto the blockchain.


---

# 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.iotex.io/ioid/technical-specification/device-nft.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.