> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/builders/morpheus-builders-api.md).

# 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:&#x20;

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](https://gitbook.mor.org/builders/morpheus-builders-api/endpoints/get-subnets.md) — list all subnets and global totals.
* [Get stakers](https://gitbook.mor.org/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
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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://gitbook.mor.org/builders/morpheus-builders-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
