# Job Procurement and Payment

## Multi-Tier Pricing (MTP)

The network has access to Multi-Tier Pricing (MTP) in order to maximize its flexibility. Depending on their requirements for speed, affordability, security, and operator repute, creators select from a variety of price categories.

* ***Tier 1** Service is the most costly, it is not subject to pricing discounts; instead, the Tier 1 multiplier is always 1. With access to GPUs with more VRAM for scenes with high complexity, jobs in Tier 1 service are given top priority and are processed through a distinct pool of certified nodes.*
* *With the most parallel GPU nodes and the best performance, **Tier 2** Service is the pinnacle of decentralized processing. Based on network circumstances, Tier 2 enjoys a pricing savings multiplier ranging from 2 to 4 in comparison to Tier 1.*
* *Although jobs process more slowly and running nodes may have less sophisticated GPU hardware than those in Tier 2, **Tier 3** Service nonetheless makes an effort to guarantee that all jobs are completed. The largest discount multiplier is seen in Tier 3 service, which can normally range from 8 to 16 based on network circumstances.*

The tier and pricing structure can be dynamically expanded in response to shifting supply and demand. Examples of such modifications include the introduction of high-performance or specialized tiers, AI computing tiers with AI hardware, tiers with renewable energy sources, and other additions as network users' preferences change over time.


---

# 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://sibylnetwork.gitbook.io/docs/job-procurement-and-payment.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.