Skip to content

Sources & collectors

The source catalog, enable/disable semantics, budget caps for metered lanes, and auto-disable.

How collection works

Each registered source has a dedicated collector that continuously pumps verified entropy into its tier pool — but only while the source is enabled. Disabling a source stops its collector within one poll cycle (fail-closed). Paid, metered lanes such as the IQM QPU are demand-driven and byte-capped rather than free-running.

Source catalog

Source IDProviderKindTier
iqm_resonance_001IQM Resonance QPUQPUQuantum verified · metered
curby_q_jila_001CURBy-Q · Bell-test (JILA)QPUQuantum verified
ql_lab_001Quantum Light (USB)QRNGQuantum verified
anu_aws_001ANU QRNG (API key)QRNGHighest quality
qispace_kds_001QiSpace tQRND (enterprise node)QRNGHighest quality
curby_rng_jila_001CURBy-RNG (JILA)QRNGHighest quality
nist_beacon_001NIST Beacon v2BeaconHighest quality · diffusion-only
rdseed_local_001x86 RDSEED + JitterHardwareFastest

Note

Diffusion-only feeds (public beacons) are credited zero secret entropy in multi-source extraction; metered sources surface budget controls in the dashboard and the API.

Enabling & disabling

Toggle a source from the Collectors page or via the admin API:

bash
# disable a source (its collector pauses within one poll)
curl -X PATCH http://localhost:8080/api/v1/sources/iqm_resonance_001 \
  -H 'content-type: application/json' \
  -d '{"enabled": false}'

Budget caps

Cap a metered source's spend by limiting the bytes its collector may draw:

bash
curl -X PATCH http://localhost:8080/api/v1/sources/iqm_resonance_001 \
  -H 'content-type: application/json' \
  -d '{"budget_cap_bytes": 1048576}'

Auto-disable

Important

A collector whose upstream API returns forbidden or quota-exhausted disables itself and reports the reason on the Collectors page. Fix the upstream credential or quota, then re-enable the source explicitly — it will not re-enable itself.