# Morpheus Builders API

The Morpheus Builder Ecosystem was designed to allow **builders** to create **subnets** where users can **stake MOR** to gain access to their services.

Subnets incentivize staking by offering perks. Examples: product access, airdrops, premium tiers.

Subnets are rewarded with **MOR emissions,** which are currently proportional to the MOR staked to their subnet.

{% hint style="info" %}
In the future, emissions will also factor in subnet utilization of the Morpheus Inference Marketplace.
{% endhint %}

For subnets to properly provide users with access to their services, they need a simple & sustainable method to access blockchain data to determine: 

1\) Who is staking to their subnet?

2\) How much MOR are they staking?

This data is now available through the **Morpheus Builders API**

You can call these endpoints from code or directly via URL.

### Base URLs

```plaintext
https://dashboard.mor.org/api/builders/subnets
```

```
https://dashboard.mor.org/api/builders/stakers
```

### Network

Responses are for the **Base** network. Amounts are in **wei** unless the field ends with `Formatted`.

### Endpoints

* [Get subnets](/builders/morpheus-builders-api/endpoints/get-subnets.md) — list all subnets and global totals.
* [Get stakers](/builders/morpheus-builders-api/endpoints/get-stakers.md) — list stakers for a subnet (paged).

### Common use cases

* Gate access based on stake.
* Build staker lists and leaderboards.
* Track subnet growth.


---

# 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://gitbook.mor.org/builders/morpheus-builders-api.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.