Suppliers
Become a supplier
Apply, get verified, and have a route attached before you list capacity.
On this page
Suppliers sell inference capacity they're authorized to sell. Cairva verifies every supplier before they can quote, and only lists capacity from verified suppliers.
Who can supply
You need a deployment that serves a model through an OpenAI-compatible chat completions endpoint, such as vLLM, SGLang, TGI or Ollama, and the right to sell access to it. Many providers make API credits non-transferable, so reselling credits bought elsewhere doesn't qualify.
Apply
- Sign in and create a supplier organization.
- Open Verification in the workspace and fill in the application. Only an organization admin can submit it.
- Cairva operations review it and decide.
The application asks for:
| Field | Notes |
|---|---|
| Legal name, jurisdiction | The entity that will sign agreements |
| Registration number | Optional |
| Website | |
| Contact name and email | Who Cairva talks to about the application |
| Models | What you can serve |
| Regions | Where it runs. At least one |
| Capacity provenance | Where the capacity comes from: your own hardware, a reserved cloud deployment, and so on |
| Authorization evidence | Why you're allowed to sell it |
| Beneficiary | Who gets paid under agreements |
Verification states
| State | Meaning |
|---|---|
applied | The organization exists, no application yet |
reviewing | Submitted and waiting for operations |
verified | Approved. You can list lots and quote |
rejected | Not approved. The reason is shown, and you can update the application and resubmit |
suspended | Verification withdrawn. Your active lots are paused |
You can edit the application until you're verified. Every decision is recorded with the reviewer's reason.
Routes
A route connects a model on your deployment to Cairva's gateway. Cairva operations create routes for verified suppliers. The endpoint credentials are configured on Cairva's servers, are never shown in the workspace and never leave the gateway.
Each route has a model, the model id your endpoint expects, a region, and a mode: live or sandbox. A route is checked for health before any agreement on it activates. See Delivery and metering.
Once you have a route, list capacity on it as inventory lots.