> For the complete documentation index, see [llms.txt](https://docs.stargaze.zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stargaze.zone/developers/overview.md).

# Overview

Technical information for developers integrating with Stargaze on the Cosmos Hub.

## Architecture

Stargaze runs on the **Cosmos Hub** using CosmWasm smart contracts. All NFT collections use the **CW721** standard.

## Contract Standard

Stargaze uses CW721 (Cosmos NFT standard) with extensions for:

* Royalty payments
* Collection metadata
* Migration support

See [CW721 Contract Reference](/developers/cw721-reference.md) for message specs.

## Chain Information

| Property          | Value       |
| ----------------- | ----------- |
| Chain             | Cosmos Hub  |
| Chain ID          | cosmoshub-4 |
| Token             | ATOM        |
| Contract Standard | CW721       |

## Querying NFT Data

To query NFT data on-chain, use standard CosmWasm contract queries against the collection contract address.

For indexed data (listings, sales history, etc.), contact the Stargaze team for API access.

## Building on Stargaze

Stargaze operates on the Cosmos Hub. For general Cosmos development:

* [Cosmos SDK Documentation](https://docs.cosmos.network)
* [CosmWasm Documentation](https://docs.cosmwasm.com)
* [CW721 Spec](https://github.com/CosmWasm/cw-nfts)

## Stargaze Names

Names are CW721 NFTs with an address resolver and a fixed-term lease, and everything about them is queryable on-chain without an API key. See [Integrating Names](/stargaze-names/integrating-names.md) for contract addresses, forward and reverse resolution, the lease state machine, and indexing notes.

## API Access

Stargaze APIs and indexer access are not publicly available. For integration partnerships, contact the team via Discord.


---

# 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.stargaze.zone/developers/overview.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.