Skip to Content

Examples

Common usage patterns for atl-cli.

Verify single file

Basic verification with auto-detected online/offline mode:

atl-cli verify document.pdf document.pdf.atl

Output shows verification result and receipt details (tier, timestamp, anchors).

Force offline verification

Skip anchor checks for faster verification or air-gapped systems:

atl-cli verify document.pdf document.pdf.atl --offline

Performs only cryptographic proof verification without checking TSA or Bitcoin anchors.

Require online verification

Fail if internet is unavailable (ensures anchor verification):

atl-cli verify document.pdf document.pdf.atl --online

Exits with error if no internet connection is available.

Batch verification

Verify all files in a directory:

atl-cli verify ./documents/ ./receipts/
  • Matches files to receipts by filename
  • Verifies each file individually
  • Performs cross-receipt log consistency checks
  • Reports summary of all verifications

Detailed output

Show each verification step:

atl-cli verify document.pdf document.pdf.atl --verbose

Displays:

  • File hash calculation
  • Merkle proof verification steps
  • Super-Tree verification
  • Anchor checks (online mode)
  • Detailed error information on failure

JSON output

For scripting and integration:

atl-cli verify document.pdf document.pdf.atl --json

Returns structured JSON with verification results, receipt details, and any errors.

Quiet mode

Only exit codes, no output:

atl-cli verify document.pdf document.pdf.atl --quiet echo $? # 0=VALID, 1=INVALID, 2=ERROR

Useful for scripts and automation.

Inspect receipt

View receipt contents without verifying file:

atl-cli inspect document.pdf.atl

Shows:

  • Entry ID and payload hash
  • Merkle tree details (size, root hash, inclusion proof)
  • Super-Tree proof details
  • Checkpoint data (timestamp, signature)
  • Anchors (TSA, Bitcoin OTS)
  • Receipt tier classification

Inspect with JSON

atl-cli inspect document.pdf.atl --json

Returns receipt structure as JSON for programmatic processing.

CI/CD integration

Example GitHub Actions workflow:

- name: Verify evidence receipts run: | atl-cli verify ./artifacts/ ./receipts/ --json > verification.json if [ $? -ne 0 ]; then echo "Verification failed" exit 1 fi

Script integration

Example verification script:

#!/bin/bash set -e for file in evidence/*.pdf; do receipt="${file}.atl" if ! atl-cli verify "$file" "$receipt" --quiet; then echo "FAILED: $file" exit 1 fi echo "OK: $file" done
Last updated on