# Ecosystem Diagrams

{% tabs %}
{% tab title="Overview" %}

<figure><img src="/files/RqanNxsDwlex6Feu2sg8" alt=""><figcaption></figcaption></figure>

This is a high-level overview of the [SlamNet Ecosystem](/welcome-to-slamai/our-ecosystem.md). Click on the tabs above for detailed diagrams of each of the SlamNet platforms.
{% endtab %}

{% tab title="SlamLink" %}

<figure><img src="/files/OWRA0n5DW0KqkAuezQtz" alt=""><figcaption></figcaption></figure>

1. The data provider supplies raw, decoded or enriched blockchain data or external data that originates off-chain
2. These data sources are proposed to the [SlamNet DAO](/governance/slamai-dao.md) by [.slam NFT](/tokens/.slam-nft.md) holders as SLAM Curation Proposals (SCPs)
3. Approved data is integrated into the [SlamLink](#slamlink) pipeline
4. Builders and end-users purchase provisioned access to the data pipeline
5. Pipeline costs are consumed with [$SLAM](/tokens/slam.md), either from the dApp (builder) or the end-user, based on data provisioned for usage.
   * (a) API fees are paid to external data providers based on data usage
   * (b) DAO Treasury receives the provisioned data fees
     {% endtab %}

{% tab title="SlamChain" %}

<figure><img src="/files/Fhngq1TQh6wWnSFZ9dAU" alt=""><figcaption></figcaption></figure>

1. A data provider, through [.slam NFT](/tokens/.slam-nft.md) holders, writes a SLAM Curation Proposal (SCP) which is sent to the [SlamNet DAO](/governance/slamai-dao.md) for approval
2. Members of the DAO's [House of SLAM](/governance/house-of-slam.md) consider the SCP for inclusion on [SlamChain](/platforms/slamchain.md)
3. If the SCP is passed:
   * (a) The enriched data is ingested  (gas-free) onto SlamChain
   * (b) The approved data provider enters into a licensing agreement with the SLAM Foundation
4. Builders use SlamChain's enriched data to build dApps
5. Users interact with dApps and pay transaction fees
6. * (a) Gas fees are distributed to the SlamNet DAO Treasury
   * (b) Volume-based transaction fees are paid to approved data providers and the SlamNet DAO Treasury
7. Users who also own .slam NFTs are members of the SlamNet DAO and can participate in [SlamNet governance](/governance/slamai-dao.md)
8. The SlamNet DAO submits SLAM Improvement Proposals (SIPs) on how to best allocate the SlamNet DAO Treasury
9. The Treasury provides grants to builders to incentivize the growth of the [SlamNet ecosystem](/welcome-to-slamai/our-ecosystem.md)
   {% endtab %}

{% tab title="SlamX" %}

<figure><img src="/files/IeIytMIdHpOl2UTvgE1p" alt=""><figcaption></figcaption></figure>

1. A content creator or engineer, through .slam NFT holders, writes a SLAM Curation Proposal (SCP) which is sent to the [SlamNet DAO](/governance/slamai-dao.md) for approval
2. Members of the DAO's [House of SLAM](/governance/house-of-slam.md) consider the SCP for inclusion on [SlamX](/platforms/slamfun.md)
3. The DAO Treasury provides grants and incentives to engineers and content creators
4. Engineers and (optionally) content creators access the [SlamLink](/platforms/slamagent.md) data pipeline for data-driven applications that feed content onto SlamX
5. Development incentives and provisioned access to the data pipeline are paid using [$SLAM](/tokens/slam.md) from the grant, which goes to the data provider and the DAO Treasury
6. * (a) Engineers use this data within AI models to create various content for SlamX
   * (b) SlamX content creators produce videos and write articles that highlight insights from the enriched data available through the [SlamNet ecosystem](/welcome-to-slamai/our-ecosystem.md)
7. The SlamNet DAO assigns an editor to review the articles written by human authors and AI-models
8. The editor approves the articles for publishing on SlamX
9. End-users access content either directly via SlamX or indirectly through syndication partners
10. End-users can optionally tip their favorite SlamX creators using $SLAM
    {% endtab %}
    {% endtabs %}


---

# 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://docs.slamai.xyz/welcome-to-slamai/our-ecosystem/ecosystem-diagrams.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.