Docs

API quickstart.

Create an API key in the console, then request entropy. Every response discloses its source class and returns an attestation hash you can store alongside the key you derived.

1. Authenticate

Keys are prefixed qsol_ and shown in full exactly once at creation. Send them as a bearer token.

Authorization: Bearer qsol_...
Content-Type: application/json

2. Request entropy

POST /functions/v1/entropy-serve
Authorization: Bearer qsol_...
Content-Type: application/json

{ "bytes": 32, "client_ref": "optional" }

200 OK
X-QSOL-Source-Class: os_entropy
X-QSOL-Attestation: 9f2c...e41

{
  "entropy_b64": "...",
  "request_id": "...",
  "source_class": "os_entropy",
  "attestation_hash": "..."
}

3. Run a validation scan

Post an algorithm manifest to receive a readiness score and severity-ranked findings.

POST /webhook/qsol/validation-scan

{
  "org_id": "org_...",
  "name": "edge-tls-2026",
  "manifest": { "algorithms": ["RSA-2048", "ML-KEM-768", "X25519"] }
}

Source class disclosure

os_entropy is the default source class: bytes come from the platform CSPRNG of the serving runtime. Other source classes are only returned when explicitly provisioned for your organization, and the class is always present in both the response body and the response header.