> For the complete documentation index, see [llms.txt](https://inferra.gitbook.io/inferra-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inferra.gitbook.io/inferra-docs/inferra-cloud/becoming-a-provider.md).

# Becoming a provider

Supply on Inferra is curated. Every listing has to be real hardware, so a person checks each provider before any capacity goes live. That is what makes the "verified" badge mean something: a verified provider is one someone actually reviewed, and a bonded provider has real, slashable money behind their word.

### The path

1. **Apply.** Tell us about your organization, how to reach you, and the hardware you run. You can apply from the Providers page or email `providers@inferra.trade`.
2. **Review.** We check the datacenter and get in touch. There is no self-serve path and no bots.
3. **Bond stake.** Once approved, you lock stake on-chain as collateral against non-delivery. This is what backs your listings.
4. **List and deliver.** Your capacity goes on the marketplace, and you get paid as you deliver it.

### What it costs and what you earn

You bond stake to list, starting at 100 USDC. If you fail to deliver on an order, part of that stake is slashed and the buyer is made whole, so your collateral is a real promise, not a formality.

When you deliver, you are paid straight from the buyer's escrow, in USDC, the same day. You keep 98%; the protocol fee is 2%. Nothing is paid before delivery, and nothing else is taken from you.

Every order you complete builds an on-chain track record: how much you have delivered, and how reliably. Reputation is public and cannot be faked, so good providers stand out over time.

### Listing capacity

You list capacity in GPU-hours over a term. A single A5000 running for a month, for example, is a straightforward listing you commit and deliver against. The marketplace prices your capacity at the live [GPU-hour index](/inferra-docs/the-ecosystem/the-gpu-hour-index.md), so you are always offering a real market rate.

To get started, read the [Inferra Cloud overview](/inferra-docs/inferra-cloud/overview.md) and [The delivery layer](/inferra-docs/inferra-cloud/the-delivery-layer.md), then apply from the Providers page or email `providers@inferra.trade`.


---

# 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://inferra.gitbook.io/inferra-docs/inferra-cloud/becoming-a-provider.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.