> For the complete documentation index, see [llms.txt](https://blendr-network.gitbook.io/blendr-network-technical-plan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blendr-network.gitbook.io/blendr-network-technical-plan-docs/blendrs-decentralized-architecture/resource-allocation.md).

# Resource Allocation

Involves two categories: Job Allocation and Node Allocation.

Job Allocation is driven by a Creator's reputation score, scene complexity, and the availability of concurrent GPU nodes. This ensures that tasks are distributed to nodes that can efficiently handle them, optimizing network resources.

Node Allocation assigns rendering tasks based on node performance (OBh scores), hardware specifications, and the node's reputation score. This ensures that the most capable and reliable nodes are selected for rendering tasks.


---

# 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://blendr-network.gitbook.io/blendr-network-technical-plan-docs/blendrs-decentralized-architecture/resource-allocation.md?ask=<question>&goal=<endgoal>
```

`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.