> 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/guardian/hedera.md). # Hedera Hedera is the section of Guardian where you manage the network-level resources — tokens, contracts, and relayer accounts — that a published policy relies on to mint, transfer, and retire digital environmental assets on the Hedera network. ### Reference * **Tokens** — fungible or non-fungible tokens created through the Hedera Token Service, with configurable Admin, Supply, Freeze, KYC, and Wipe permissions. * **Contracts** — includes Token Wiping Contracts and Token Retirement Contracts, that together handle permissioned, atomic retirement of tokens. * **Relayer Accounts** — funded Hedera accounts that pay for and execute a policy's on-chain transactions, so costs can be isolated per project instead of per user. ### Related * [Tokens](/docs/develop/guardian/hedera/tokens.md) * [Contracts](/docs/develop/guardian/hedera/contracts.md) * [Relayer Accounts](/docs/develop/guardian/hedera/relayer-accounts.md) --- # 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/guardian/hedera.md?ask=&goal= ``` `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.