> For the complete documentation index, see [llms.txt](https://docs.cindereth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cindereth.com/site/sharing-your-burns.md).

# Sharing Your Burns

Every burn and every history row can become a share card: your numbers drawn onto Cinder's furnace artwork, sized for X.

## From a burn

When a burn completes, the card is generated automatically in the result window. **Post on X** opens a prefilled post; **Save image** downloads the card to attach.

## From your Profile

**Share on X** at the top shares your wallet totals. The **Share** button on any row shares that single action.

X cannot attach an image from a link, so the flow is two steps everywhere: save the image, then drop it into the post the button opened.

Token names are sanitized before they reach a post, so a token that names itself after a scam URL cannot advertise through your share.


---

# 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.cindereth.com/site/sharing-your-burns.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.
