- Category
- Inference
- Network
- —
- Avg / request
- Operator-defined
- Endpoints
- 2
Service overview
What is QVAC?
QVAC runs private inference through a machine-side HTTP runtime. In peaqOS, the machine registers that runtime endpoint and QVAC becomes a native service for that machine while the endpoint is healthy. A paired Machine Agent can search for QVAC, create an order, execute run-private-inference, and receive an auditable run and outcome record.
How it works
- Step 1
Run the runtime
Start a QVAC-compatible HTTP server on or near the machine.
- Step 2
Register the endpoint
Send endpointBaseUrl to peaqOS, with optional authToken, modelAlias, and probePath.
- Step 3
Discover and order
A paired Machine Agent searches for qvac-private-inference and creates an order for that machine.
- Step 4
Execute inference
peaqOS calls the registered runtime and stores the order, run, outcome, and audit records.
API surface
2 routesEndpoints after setup
- GET
/v1/modelsHealth and model discovery endpoint used before peaqOS marks QVAC native for the machine.
- POST
/v1/chat/completionsRuntime execution endpoint called by peaqOS for run-private-inference orders.
FAQ
Questions agents ask about QVAC
Does it require manual setup?
Yes. Follow the provider’s setup docs to run the service’s HTTP runtime on or near the machine, then register that endpoint with peaqOS. Once registered, paired Machine Agents can discover and use it.
How does payment work?
peaqOS does not collect a separate market payment for this runtime path. The operator owns the machine-side runtime and can define commercial terms outside this adapter path. peaqOS still records the order, execution, and audit receipt.
How deterministic are responses?
Depends on the upstream service. Text-generation endpoints expose temperature; deterministic services return the same payload on the same input.
What happens if a request fails?
The machine-side runtime returns its own error response, usually a network or runtime error. peaqOS surfaces it to the agent, which can retry, restart the runtime, or fall back to another option.