IonQ v0.4Real job IDCustomer-fundedNot key material

Bind a ZME1 commitment to real quantum-cloud evidence.

The container is hashed locally. Only its SHA-256 commitment is submitted in IonQ job metadata alongside a one-qubit circuit. The returned job ID is external provenance evidence, not an encryption key and not quantum key distribution.

Checkingdeployment

Checkingbackend policy

0plaintext uploads

Create an IonQ commitment receipt

This form works on a customer server after its administrator installs an IonQ API key and a separate ZMath deployment token outside the web root.

ZME1 container IonQ backend Deployment access token

This is not the IonQ API key. The IonQ key stays server-side. The deployment token is cleared after submission.

Ready. The live TalkToAI server fails closed unless its owner configures this lane.

Cost control: QPU targets are disabled until the customer administrator creates the explicit hardware-enable file. A per-deployment daily job limit applies. Review IonQ pricing before enabling paid hardware.