> For the complete documentation index, see [llms.txt](https://docs.bogged.finance/bogged-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bogged.finance/bogged-finance/token-teams/bogcharts/bogcharts-for-token-teams.md).
# BogCharts for Token Teams
If you have not yet done so, you can create a chart embed [**here**](https://teams.bogged.finance/chart).\
\
There are two types of chart embeds: [**iframe**](#iframe) and [**Web Component**](#web-component)
## iframe
Iframe code can be placed anywhere in your HTML code with no additional scripts.\
You can style the iframe with CSS just like any other HTML element.\
\
**Example:**
```html
```
## Web Component
A Web Component is a new web technology to create reusable custom elements with their functionality encapsulated away from the rest of your code.\
\
For the Chart Web Component, you can modify any property on the element to have it update in real-time. You can also listen to the **onUpdate** event to get price information as the chart updates.
#### **Exposed Price Information**
```typescript
{
"baseSymbol": string,
"baseAddress": string,
"baseDecimals": number,
"basePriceUSD": number,
"baseCircSupply": number,
"baseTotalSupply": number,
"baseMarketcap": number,
"baseMarketcapFD": number,
"quoteSymbol": string,
"quoteAddress": string,
"quoteDecimals": number,
"quotePriceUSD": number,
"tokensPerQuote": number,
"singleLPValueUSD": number,
"totalLiquidityUSD": number,
"pairAddress": string,
"pairFactory": string
}
```
### Examples
#### **Dynamically Changing Chart Type**
```html
```
{% embed url="" %}
**Changing Chart Type Example**
{% endembed %}
#### **Listening To Chart Update**
```html
```
{% embed url="" %}
Accessing Chart Update Example
{% endembed %}
---
# 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.bogged.finance/bogged-finance/token-teams/bogcharts/bogcharts-for-token-teams.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.