> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/protocol/metadata-and-ipfs.md).

# Metadata and IPFS

Hatchr stores token metadata through a public IPFS URI written during initialization.

## Metadata fields

Metadata can include:

* token name;
* symbol;
* description;
* image URI;
* X link;
* Telegram link; and
* website link.

The Hatchr application pins the image and metadata JSON through Pinata before the launch transaction.

## On-chain reference

The token exposes `metadataURI`. It has no setter, so Hatchr cannot replace the URI after initialization.

## IPFS and gateways

IPFS is content-addressed. The CID identifies the content, while gateways provide HTTP access to it. Gateway availability is not the same as content identity.

Hatchr normalizes `ipfs://` links for display and can use gateway fallbacks. Integrators should retain the original CID and avoid treating one gateway hostname as canonical.

## Trading-terminal logos

External terminals maintain their own crawlers, moderation and caches. A token can trade before a third party ingests its image. Publishing correct IPFS metadata does not force immediate display on Dexscreener, GMGN or another service.


---

# 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://docs.hatchr.fun/protocol/metadata-and-ipfs.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.