> 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/ioid-depin-identities.md).

# ioID Identity for Machines and Agents

{% hint style="info" %}
**Note:** The documentation for ioID is actively being updated. Check back soon for updates or if you have feedback please
{% endhint %}

IoID is a decentralized identity framework purpose-built to **establish trust in the machine economy**, enabling smart agents and **physical AI** to interact securely and autonomously. 

IoID includes both on-chain and off-chain components:

* **On-Chain Identity**: 

  Each machine is represented by an NFT-bound smart contract wallet, enabling it to manage digital assets, receive rewards, and participate in decentralized applications (dApps) and DeFi protocols.
* **Off-Chain Identity**: 

  ioID integrates self-sovereign identity (SSI) standards—including decentralized identifiers (DIDs) and verifiable credentials (VCs)—to support secure, privacy-preserving communication between machines and humans (M2P) or other machines (M2M).

This section of the documentation covers the concepts, architecture, and integration details of ioID, along with use cases and practical guidance for developers integrating decentralized identity into machine-based applications.


---

# 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/ioid-depin-identities.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.