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

# Explorers Overview

Guardian produces data as activity flows through the platform. This includes primatives such as projects, credits, policies, methodologies, organizations, and verification documents. 

**Explorers** are dedicated applications that surface data published to the [Hedera Network](https://hedera.com/) for different audiences, each presenting the same underlying information through a lens suited for specific jobs and purposes.

Three explorers exist today, ranging from a technical developer tool to polished, business-focused market intelligence platforms. All three are open source and hosted in the Guardian repository.

***

### The three explorers

<table><thead><tr><th width="221.25390625">Explorer</th><th>Audience</th><th>Focus</th></tr></thead><tbody><tr><td>Sustainability Atlas</td><td>Carbon market participants e.g. buyers, auditors, project developers</td><td>Business intelligence e.g. projects, credits, methodologies, and reporting through a market lens</td></tr><tr><td>Guardian Indexer</td><td>Developers, registry operators, technical users</td><td>Complete on-chain record e.g. every document, policy, schema, and token, searchable in raw form</td></tr><tr><td>Carbon Atlas</td><td>Policy-specific users and market analysts</td><td>Per-methodology deep dives and cross-registry market analytics</td></tr></tbody></table>

***

### Why multiple explorers?

Guardian's data is rich and context specific. A developer debugging a policy workflow can inspect raw Verifiable Credentials and topic hierarchies. A carbon credit buyer can compare projects by vintage, geography, and SDG alignment. An asset manager or compliance officer can generate a  reports with traceability references.&#x20;

Each explorer is an independent application with its own data model, interface, and deployment which all draw from the same Guardian-generated data on Hedera and IPFS.

***

### At a glance

**Sustainability Atlas** — A business intelligence platform that translates on-chain data into the language of the carbon market: Projects, Credit Issuances, Retirements, Methodologies, and Organizations. Built for market participants who need to find, analyze, and report on carbon credits without blockchain expertise.

**Guardian Indexer** — The foundational explorer. Indexes the complete output of every Guardian instance and presents it as a searchable, navigable record. The Indexer is the primary source of truth for technical users who need to inspect the on-chain state of any policy, credential, or account.

**Carbon Atlas** — A policy-specific explorer focused on verified emission reductions. Provides deep per-methodology views (trust chain, project lifecycle, monitoring reports) alongside a cross-registry market overview spanning projects across major carbon standards.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guardian.hedera.com/docs/develop/explorers/explorers-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.