Skip to content

Verification

Don't trust SIX. Verify.

SIX is designed so that you never need to trust the infrastructure provider. Every receipt is independently verifiable using mathematics, not promises. This section covers how to verify that your AI inferences actually ran, ran where you specified, and were not tampered with.

Why Independent Verification Matters

Most AI providers ask you to trust them. SIX gives you proof instead.

Traditional AI SIX
"We processed your request" Signed receipt you can verify yourself
"Your data stayed in-region" Routing attestation bound to cryptographic proof
"We didn't modify the response" Tamper-evident commitment -- any change breaks the proof
"Here's your invoice" Settlement anchored to an immutable ledger

For regulated industries, the distinction matters:

  • Auditors want mathematical proof, not vendor assurances
  • Compliance officers need independent verification they can demonstrate
  • Legal teams need e-discovery-ready proof that stands up in court

Three Verification Methods

SIX provides three ways to verify receipts, ordered from simplest to most rigorous.

1. API Endpoint

The simplest method. Send the receipt ID to the verification endpoint and receive a verification result.

curl https://six-sov.com/v1/verify/rcpt_f8c505ce3a... \
  -H "Authorization: Bearer $SIX_API_KEY"

Best for: Automated verification pipelines, application-level checks.

Limitation: You are asking SIX to verify its own receipt. Sufficient for most use cases, but auditors may want stronger independence.

API Verification Reference -->

2. CLI Tool

A locally-running verification tool that checks receipts without contacting SIX infrastructure. The tool uses the SIX public key to validate signatures and recompute commitments entirely on your machine.

six verify receipt.json

Best for: Audit preparation, compliance demonstrations, air-gapped environments.

Advantage: Fully independent -- no network call to SIX. The verification runs on your infrastructure using published public keys.

CLI Verification Tool
The CLI verification tool is provided to approved partners under NDA. It includes local signature validation, commitment recomputation, and ledger anchor verification.

Request CLI tool access →

3. Manual (Cryptographic)

For maximum assurance, you can verify receipts using standard cryptographic libraries in any language. This requires:

  1. The SIX public key (published)
  2. The receipt fields
  3. A cryptographic library capable of signature verification

This method provides zero-trust verification -- you do not depend on any SIX-provided software.

Manual Verification Guide
The manual verification procedure, including commitment recomputation algorithm and signature verification steps, is documented in the full technical specification.

Request verification specification →

Verification Comparison

Method Independence Ease of Use Requires Network Best For
API Endpoint Medium Easy Yes Automated pipelines
CLI Tool High Medium No Audit preparation
Manual Maximum Advanced No Zero-trust environments

What Gets Verified

Every verification method checks the same properties:

Check Question Answered
Commitment validity Were any receipt fields modified after issuance?
Signature authenticity Was this receipt issued by authorized SIX infrastructure?
Routing confirmation Did the inference run on the specified compute path?
Attestation integrity Is the execution attestation intact and untampered?
Settlement anchor Is the settlement anchored to the immutable ledger?

Verification for Compliance

Different regulatory frameworks have different verification requirements:

Framework Requirement SIX Verification
HIPAA Audit controls (164.312(b)) Receipt verification creates audit trail
SOX Internal controls documentation Receipts provide mathematical proof of AI decision integrity
GDPR Data processing verification Routing field proves data boundary enforcement
FRCP E-discovery admissibility Cryptographic proof of integrity withstands legal challenge

See Compliance Guides for framework-specific details.

Next Steps