# Ecosystem Roles

### **Content Providers** :tv:

These are content owners and developers of live streaming, over-the-top (OTT) media, and gaming platforms reaching a large number of clients. They pay for efficient, accelerated downloads and high bitrate streaming from their media origin to their end-user audience or device fleet.

### **Node Operator** :seedling: (That could be you!)

Node operators run cache servers as part of the Blockcast content delivery network. In return for providing resources like bandwidth and electricity, and for maintaining the node's uptime, they earn weekly rewards for serving content.

There are three distinct types of nodes in the Blockcast network:

1. [RECEIVE](https://docs.blockcast.network/main/getting-started/how-do-i-participate-in-the-network/beacon) 
2. [RELAY](https://docs.blockcast.network/main/getting-started/how-do-i-participate-in-the-network/relay) 
3. [CAST](https://docs.blockcast.network/main/getting-started/how-do-i-participate-in-the-network/cast) 

### **Internet Service Provider (ISP)** :globe\_with\_meridians:

Transit and/or access network provider for node operators and end users. While this typically refers to major providers like Verizon or Comcast, there are also smaller Wireless ISPs (WISPs)—with over 3,000 in the United States alone.

ISPs can operate CDN nodes as part of the Blockcast Network. They benefit from:

* Receiving revenue share as node operators
* Reducing network congestion by running local caching facilities
* Improving service quality for their users

### **Broadcasters** :satellite:

Broadcasters are satellite or TV broadcast spectrum holders who monetize their unused capacity through Blockcast’s marketplace to scale the delivery of popular content to mass audiences. 

### **End User** :person\_bald::girl:

End users are the primary beneficiaries of the network. Participating content providers steer them transparently to the nearest RELAY node with no active participation needed from the user.

<br>

<figure><img src="https://3364791352-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXrwmDBB6htefs8IbVcEc%2Fuploads%2FfEUSauY42bdSClNHWzcy%2FF_JdgzGXYAAh8dq.jpeg?alt=media&#x26;token=c3da9512-cec8-40ec-ae4b-4ee9eac21c5d" alt=""><figcaption></figcaption></figure>


---

# 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.blockcast.network/main/overview/ecosystem-roles.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.