> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ixo.world/llms.txt
> Use this file to discover all available pages before exploring further.

# Domain Registration

> Create and manage digital twins of real-world entities using the IXO Stack

<Tip>
  Domains are used to create digital twins of real-world entities.
</Tip>

## Quick Start

<CodeGroup>
  ```bash Create Domain theme={"system"}
  curl -X POST https://api.emerging.eco/v1/domains \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -d '{
      "type": "Project",
      "protocol": "did:ixo:protocol/clean-cooking",
      "metadata": {
        "name": "Clean Cooking Project"
      }
    }'
  ```

  ```python theme={"system"}
  from emerging import Client

  client = Client('YOUR_API_KEY')
  domain = client.domains.create(
      type="Project",
      protocol="did:ixo:protocol/clean-cooking",
      metadata={
          "name": "Clean Cooking Project"
      }
  )
  ```
</CodeGroup>

## Domain Types

<CardGroup>
  <Card title="Organisations" icon="building">
    Legal or virtual entities, managed as DAOs
  </Card>

  <Card title="Projects" icon="diagram-project">
    `Project` type entities for clean cooking initiatives
  </Card>

  <Card title="Assets" icon="microchip">
    `Asset` type entities for IoT-enabled cooking devices
  </Card>

  <Card title="Protocols" icon="file-code">
    Templates and rules that govern domain behavior
  </Card>

  <Card title="Oracles" icon="sparkles" />

  <Card title="Requests" icon="sparkles" />
</CardGroup>

## Domain Properties

Each domain requires:

* **Digital Identifier**: Unique DID following Interchain Identifier format

* **Entity Type**: Organisation, Project, Device, etc.

* **Protocol**: Defines the Class of entity and its inherited sets of properties

* **Controller**: Account/s that manage the domain record (DID Document)

* **Metadata**: Additional standard domain settings

## Creating Domains

### Required Parameters

<ResponseField name="type" type="string" required>
  Entity type (Organisation, Project, Device, etc.)
</ResponseField>

<ResponseField name="class" type="string" required>
  DID of the Protocol that defines the Entity Class
</ResponseField>

<ResponseField name="metadata" type="object">
  Domain settings of the Entity
</ResponseField>

### Optional Parameters

<ResponseField name="validFrom" type="string">
  ISO timestamp when domain becomes valid
</ResponseField>

<ResponseField name="validUntil" type="string">
  ISO timestamp when domain expires
</ResponseField>

## Domain Verification

Domains require verification by the platform's governance system:

1. A compliance or program representative submits a verification proposal with the entity package.
2. Eligible voters review and vote (quorum and thresholds depend on deployment).
3. On approval, domain status moves to **Verified** and downstream services (reporting, issuance) can enable.

For a platform-scoped walkthrough (DAO stages, relayer assignment, GraphQL status checks), read [Emerging Platform domain registration](/platforms/Emerging/domain-registration). For how **roles** (Developer, Evaluator, Funder, Service provider) map to these steps, read [Your role](/your-role).

<Tip>
  Only verified domains can participate in platform activities like carbon credit issuance. Confirm auth and endpoints for your environment in the [Authentication matrix](/reference/authentication-matrix) and [Networks and endpoints](/reference/networks-and-endpoints).
</Tip>

## Next steps

<CardGroup>
  <Card title="Emerging domain registration" icon="globe" href="/platforms/Emerging/domain-registration">
    Governance stages, entity JSON, and GraphQL examples
  </Card>

  <Card title="Digital twins" icon="cube" href="/guides/digital-twins">
    Model entities, protocols, and relationships
  </Card>

  <Card title="Identity and credentials" icon="fingerprint" href="/articles/identity-and-credentials">
    How DIDs, claims, and verifiable credentials connect
  </Card>

  <Card title="DAOs" icon="scale-balanced" href="/articles/daos">
    How decentralized governance fits IXO programs
  </Card>
</CardGroup>