# Monetization

The primary revenue stream comes from the sale of cosmetic upgrades for Spellcards and Canvases. Users can purchase unique icons, animations, and visual effects to make their Spell Cards and Canvases more visually appealing. These upgrades are entirely optional and do not impact the functionality of the Spell Card or Canvas.

Additionally, brands can purchase advertising space on the platform by creating Spell Cards specifically designed for advertising purposes. These Spell Cards will be marked as "Ads" and users can choose to hide them from their searches if they wish.

Finally, Spellcard.io can generate revenue by partnering with other companies or brands to offer exclusive Spell Cards, Canvases, or other digital products. These partnerships can also help to expand the reach of the platform and attract new users.

Overall, Spellcard.io offers a variety of monetization options that are non-intrusive and optional for users. The focus of the platform remains on providing a fun and engaging environment for users to create and share unique content in a competitive RPG-style environment.\
\
\
\- Users can pay to promote a spellcard for a period of time\
\- Users can acquire premium accounts that unlock various cosmetic options and allow them to hide paid advertisements \
\- Users can purchase various cosmetic upgrades\
\- Purchase options available to turn cards into artifacts which function as a "canvas" / "tavern" / "guild hall"


---

# Agent Instructions: 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:

```
GET https://spellcard-io.gitbook.io/spellcard.io/overview/monetization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.