No content logs#
The gateway does not persist prompts, completion content or tool arguments, and its application logs omit request bodies. Provider retention and infrastructure logging require separate verification; this is not an end-to-end zero-retention guarantee.
Accounting data#
We retain account identifiers, hashed API keys, deposits, withdrawal requests, token counters and aggregated usage. These are necessary for authentication and accounting. Zero prompt retention does not mean zero billing records.
Dedicated GPU orders retain the selected hardware and model, monthly price, payment and cancellation status, and service dates and endpoint details when provisioning is confirmed.
Regions#
Dallas, Ashburn and Portland are target GPU regions. Hardware availability, routing and data residency require confirmation for the selected deployment.
Trust and operational scope#
The trust centre explains account and accounting records, key controls, and the limits of provider-retention and regional assurances. The support guide explains what to exclude from a diagnostic report.
Request example
curl https://weightsapi.com/v1/chat/completions \
-H "Authorization: Bearer $WEIGHTSAPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "Qwen/Qwen3-32B",
"messages": [
{
"role": "user",
"content": "Hello!"
}
],
"stream": true
}'