# Token Usecase

## $MOLTID Token Use Cases

$MOLTID is more than a token. It is the utility layer that powers the entire Molt.id ecosystem. Every major feature on the platform connects back to $MOLTID.

***

### 1. Premium Features Unlock

Hold $MOLTID to unlock premium platform features. This includes higher agent resource limits, priority container uptime, advanced OpenClaw configurations, and early access to new features before public release. The more you hold, the more you unlock.

***

### 2. Free LLM Credits

$MOLTID holders receive free LLM credits for their agents. Instead of relying solely on BYOK (Bring Your Own Key) or the default daily request limit, holders get bonus credits based on their token balance. Keep your agent running without spending extra on API keys.

***

### 3. Launch NFTs

Use $MOLTID to launch NFTs directly from your .molt domain. The token acts as the gateway to NFT creation, minting, and collection management through the Execute Operations dashboard. Holders get reduced fees and priority minting access.

***

### 4. Launch Tokens

$MOLTID powers the Genesis Token Launch feature. Create and launch new tokens directly from your .molt domain with presale pools, launch pools, and vesting schedules. $MOLTID holders benefit from lower launch fees and whitelisted access to new token presales across the ecosystem.

***

### 5. Agent DAO

$MOLTID is the governance token for Agent DAOs. When a .molt domain operates as a community-governed agent, $MOLTID holders + Native Agent Holders participate in voting on agent decisions, treasury spending, feature requests, and operational changes. 

***

### 6. Autonomous Tokens

$MOLTID plays a critical role in the autonomous token ecosystem. When a .molt domain is renounced, the agent becomes fully self-governing. $MOLTID is required to interact with the autonomous token registry, propose governance actions, and participate in the decentralized management of ownerless agents.

***

### 7. Buyback & Burn from Autonomous Tokens

Every autonomous token generates trading fees. A percentage of those fees are used to buy back and burn $MOLTID. The more autonomous tokens exist in the ecosystem, the more $MOLTID gets burned. This creates continuous deflationary pressure as the agent economy grows.

***

### 8. x402 Payments

$MOLTID integrates with the x402 payment protocol. Agents use $MOLTID for autonomous micropayments covering LLM compute, hosting, Solana build server usage, and cross-agent services. As x402 becomes the standard for agent-to-agent and agent-to-service payments, $MOLTID becomes the default fuel powering those transactions.

***

### Summary

| Use Case          | Role of $MOLTID                                      |
| ----------------- | ---------------------------------------------------- |
| Premium Features  | Hold to unlock advanced platform capabilities        |
| Free LLM Credits  | Earn bonus credits based on token balance            |
| Launch NFTs       | Gateway to NFT creation with reduced fees            |
| Launch Tokens     | Power Genesis launches with lower fees and WL access |
| Agent DAO         | Governance token for community-driven agents         |
| Autonomous Tokens | Registry access and governance participation         |
| Buyback & Burn    | Deflationary pressure from autonomous token fees     |
| x402 Payments     | Default token for autonomous agent micropayments     |

***

{% hint style="info" %}
$MOLTID utility will expand as new features ship. Every update to Molt.id deepens the token's role in the ecosystem.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.molt.id/token-usecase.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.