# Quantum-Safe File Attestation ## Links - Product page URL: https://www.agentpmt.com/marketplace/quantum-safe-file-attestation - Product markdown URL: https://www.agentpmt.com/marketplace/quantum-safe-file-attestation?format=agent-md - Product JSON URL: https://www.agentpmt.com/marketplace/quantum-safe-file-attestation?format=agent-json ## Overview - Product ID: 69c99cefc3ba2714db75e12a - Type: function - Unit type: request - Price: 500 credits - Categories: Security & Cryptography, Quantum Cryptography, Developer Tools, Compliance & Audit, Data Validation & Verification, Hashing & Checksums, File & Binary Operations - Generated at: 2026-06-25T13:24:13.680Z ### Page Description Issue formally verified, post-quantum cryptographic attestation certificates for any file. Every attestation is backed by a proof-carrying certificate bundle whose acceptance logic is proven correct in Lean 4. Signing uses ML-DSA-65 from the NIST post-quantum standard, executed through PQClean standardized runtimes with the private key secured in a hardware security module. A 4-check verification pipeline confirms signature validity, manifest consistency, artifact integrity, and certificate Merkle-tree integrity — all must pass. Anyone can verify certificates independently using the open-source offline verifier. No trust in our infrastructure required. ### Agent Description Issue and verify formally verified post-quantum cryptographic attestation packages for files. Signs artifacts with ML-DSA-65 (Dilithium3) via Google Cloud KMS hardware security module using PQClean standardized byte-level runtimes. Returns proof-carrying certificate bundles (CAB) with Lean 4 formally verified acceptance kernels that cryptographically bind artifact hash, proof commitment, and manifest signature. Verification pipeline checks signature validity, manifest consistency, artifact integrity, and CAB Merkle-tree integrity. Supports freeform metadata in manifests. Export signer public key for independent offline verification via the open-source verifier. ## Details ### Details Issue formally verified, post-quantum cryptographic attestation certificates for any file. Every attestation is backed by a proof-carrying certificate bundle whose acceptance logic is proven correct in Lean 4. Signing uses ML-DSA-65 from the NIST post-quantum standard, executed through PQClean standardized runtimes with the private key secured in a hardware security module. A 4-check verification pipeline confirms signature validity, manifest consistency, artifact integrity, and certificate Merkle-tree integrity — all must pass. Anyone can verify certificates independently using the open-source offline verifier. No trust in our infrastructure required. ### Actions - `attest_artifact` (25 credits): Create a post-quantum cryptographic attestation for a file in storage. Signs with ML-DSA-65 via hardware security module. Saves the attestation package to file storage and returns its file_id. - `verify_attestation` (5 credits): Verify a previously issued attestation package against the original artifact. Both the artifact and the attestation package must be in file storage. Checks ML-DSA-65 signature, manifest integrity, artifact SHA-256 match, and CAB bundle. - `get_public_key` (5 credits): Return the signer's public key, algorithm, and fingerprint so independent verifiers can confirm attestation signatures without calling this tool. ### Use Cases Sign software releases with formally verified post-quantum cryptography, Create proof-carrying attestation certificates with Lean 4 verified acceptance kernels, Verify file integrity with NIST-standardized ML-DSA-65 digital signatures and PQClean runtimes, Generate compliance evidence for SOC 2 SOX HIPAA and regulatory audits with cryptographic proof chains, Timestamp and cryptographically attest intellectual property artifacts with tamper-evident CAB bundles, Verify software supply chain integrity with 4-check verification pipeline, Issue verifiable certificates for code repositories and release archives backed by formal proofs, Provide independent verification keys for third-party auditors and partners, Create provenance records for AI model weights and training data with quantum-safe signatures, Attest firmware images and embedded software updates with hardware-backed signing, Notarize documents with post-quantum signatures backed by information-theoretic security foundations, Sign configuration files and infrastructure-as-code with formally verified cryptographic protocol stack ### Workflows Using This Tool #### Verify File Attestation Certificate Upload a file and its attestation certificate, then cryptographically verify that the certificate is authentic and the file has not been tampered with. Uses post-quantum ML-DSA-65 signature verification. Perfect for confirming software release integrity, validating compliance evidence, or verifying any file that was previously attested. - Page URL: https://www.agentpmt.com/agent-workflow-skills/verify-file-attestation-certificate - Markdown URL: https://www.agentpmt.com/agent-workflow-skills/verify-file-attestation-certificate?format=agent-md - Published: 2026-03-30T16:52:51.960Z #### Document and File Certification with Post-Quantum Digital Signatures Generate tamper-proof digital certificates for any uploaded file using post-quantum cryptography. This workflow guides the user through uploading or selecting a file via the File Management tool, then signs it with the Quantum-Safe File Attestation tool using ML-DSA-65 (Dilithium3) post-quantum digital signatures via hardware security module. Returns a verifiable attestation package containing a cryptographic manifest, digital signature, and verification bundle with a downloadable certificate link. Use cases include regulatory compliance document certification, financial audit report signing, legal contract attestation, intellectual property timestamping, medical record integrity verification, insurance claim evidence certification, notarized document equivalents, SOC 2 and ISO 27001 audit evidence, HIPAA-compliant document signing, tax filing certification, and tamper-proof archival of sensitive business documents. - Page URL: https://www.agentpmt.com/agent-workflow-skills/document-and-file-certification-with-post-quantum-digital-signatures - Markdown URL: https://www.agentpmt.com/agent-workflow-skills/document-and-file-certification-with-post-quantum-digital-signatures?format=agent-md - Published: 2026-03-30T03:28:07.020Z #### GitHub Repository Code Signing and Attestation with Post-Quantum Cryptography Automate post-quantum code signing and software supply chain attestation for GitHub repositories and release artifacts. This workflow asks the user which GitHub repository, branch, tag, or specific file they want to certify, downloads the content using the GitHub Repo Browser tool, and signs it with the Quantum-Safe File Attestation tool using ML-DSA-65 (Dilithium3) post-quantum digital signatures via hardware security module. Returns a verifiable attestation package containing a cryptographic manifest, digital signature, and verification bundle with a downloadable certificate link. Use cases include software release signing, open source distribution integrity, SBOM attestation, build artifact certification, code audit compliance evidence, CI/CD pipeline integrity verification, regulatory submission of source code, DevSecOps supply chain security, and tamper-proof repository snapshots for legal or IP protection. - Page URL: https://www.agentpmt.com/agent-workflow-skills/github-repository-code-signing-and-attestation-with-post-quantum-cryptography - Markdown URL: https://www.agentpmt.com/agent-workflow-skills/github-repository-code-signing-and-attestation-with-post-quantum-cryptography?format=agent-md - Published: 2026-03-30T03:28:05.173Z ### Related Content #### Quantum-Safe File Attestation Launches on AgentPMT: Post-Quantum Proof for Every File - Type: article - Page URL: https://www.agentpmt.com/articles/quantum-safe-file-attestation-launches-on-agentpmt-post-quantum-proof-for-every-file - Markdown URL: https://www.agentpmt.com/articles/quantum-safe-file-attestation-launches-on-agentpmt-post-quantum-proof-for-every-file?format=agent-md AgentPMT adds Quantum-Safe File Attestation to its marketplace, giving AI agents the ability to sign and verify files using ML-DSA-65 post-quantum cryptography through a hardware security module. #### Why AI Cybersecurity Needs Quantum-Safe Signatures Now - Type: article - Page URL: https://www.agentpmt.com/articles/why-ai-cybersecurity-needs-quantum-safe-signatures-now - Markdown URL: https://www.agentpmt.com/articles/why-ai-cybersecurity-needs-quantum-safe-signatures-now?format=agent-md Every digital signature used today will break under quantum computing. A review of the Apoth3osis QSFA system shows how ML-DSA-65 and formally verified code create file attestations designed to survive the post-quantum era. ## Integration Details ### DynamicMCP - Setup page URL: https://www.agentpmt.com/dynamic-mcp - Claude setup guide: https://www.agentpmt.com/dynamic-mcp#platform=claude - ChatGPT setup guide: https://www.agentpmt.com/dynamic-mcp#platform=chatgpt - Cursor setup guide: https://www.agentpmt.com/dynamic-mcp#platform=cursor - Windsurf setup guide: https://www.agentpmt.com/dynamic-mcp#platform=windsurf Use the local router for command-based MCP clients. It forwards requests to `https://api.agentpmt.com/mcp` and does not execute tools locally. ```bash npm install -g @agentpmt/mcp-router agentpmt-setup ``` ### REST API The live page renders cURL, Python, JavaScript, and Node.js examples. Logged-in users see those examples prefilled with their own API and budget credentials. - Purchase endpoint: https://api.agentpmt.com/products/purchase - Authorization format: `Bearer ` ```bash curl -X POST "https://api.agentpmt.com/products/purchase" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer eW91ci1hcGkta2V5LWhlcmU6eW91ci1idWRnZXQta2V5LWhlcmU=" \ -d '{ "product_id": "69c99cefc3ba2714db75e12a", "parameters": { "action": "attest_artifact", "file_id": "example_file_id" } }' ``` ### Autonomous Agents Autonomous agents can access this tool through AgentAddress credit balances or direct x402 payments. Use the Autonomous Agent API reference for endpoint shapes after choosing the access pattern below. - Autonomous Agent API reference URL: https://www.agentpmt.com/docs/api-reference/autonomous-agents - Autonomous Agent API reference markdown URL: https://www.agentpmt.com/docs/api-reference/autonomous-agents?format=agent-md - Credit-Based Access Using AgentAddress: https://www.agentpmt.com/docs/autonomous-agents/credit-based-tool-usage-with-agentaddress - AgentAddress is preferred for persistent file access, stored platform state, and maximum tool use ability across repeated calls. - Direct x402 is for independent one-off tool calls that do not require shared files or stored platform state. - Direct x402 public payments: USDC on Base, Arbitrum, Optimism, Polygon, and Avalanche. #### Product Skill Package This product has a published Agent Skill package for product-specific operating instructions. - Skill slug: quantum-safe-file-attestation - Version: 1.0.0 - Download SKILL.md: https://raw.githubusercontent.com/AgentPMT/agent-skills/main/skills/quantum-safe-file-attestation/SKILL.md - Package source: https://github.com/AgentPMT/agent-skills/tree/main/skills/quantum-safe-file-attestation - OpenClaw listing: https://clawhub.ai/agentpmt/quantum-safe-file-attestation - OpenClaw install: `openclaw skills install quantum-safe-file-attestation` - skills.sh install: `npx skills add AgentPMT/agent-skills --skill quantum-safe-file-attestation` - Last published: 2026-06-24T11:14:57.781Z ### Schema #### Parameters - Schema type: actions ```json { "actions": { "attest_artifact": { "description": "Create a post-quantum cryptographic attestation for a file in storage. Signs with ML-DSA-65 via hardware security module. Saves the attestation package to file storage and returns its file_id.", "properties": { "file_id": { "type": "string", "description": "File ID from file storage (from upload or GitHub download).", "required": true }, "artifact_name": { "type": "string", "description": "Human-readable name for the artifact being attested. Defaults to the stored filename.", "required": false }, "metadata": { "type": "object", "description": "Optional freeform metadata to include in the attestation manifest.", "required": false } }, "price_per_unit": 25 }, "verify_attestation": { "description": "Verify a previously issued attestation package against the original artifact. Both the artifact and the attestation package must be in file storage. Checks ML-DSA-65 signature, manifest integrity, artifact SHA-256 match, and CAB bundle.", "properties": { "file_id": { "type": "string", "description": "File ID of the original artifact to verify.", "required": true }, "attestation_file_id": { "type": "string", "description": "File ID of the attestation package JSON (returned as attestation_file_id by attest_artifact).", "required": true }, "check_bundle": { "type": "boolean", "description": "Whether to also verify the CAB verifier bundle material. Defaults to true.", "required": false } }, "price_per_unit": 5 }, "get_public_key": { "description": "Return the signer's public key, algorithm, and fingerprint so independent verifiers can confirm attestation signatures without calling this tool.", "price_per_unit": 5 } } } ``` ### Usage Instructions # Quantum-Safe File Attestation Create and verify post-quantum cryptographic attestation packages for files using ML-DSA-65 (Dilithium3). ## Actions ### `attest_artifact` Create a cryptographic attestation for a file in storage. The attestation package is saved to file storage. Required: - `file_id` (string): file ID of the artifact to attest. Upload the file first using the File Management tool (action `upload_standard`), then pass the returned `file_id` here. Optional: - `artifact_name` (string): human-readable name (defaults to stored filename) - `metadata` (object): freeform key-value pairs to include in the manifest ```json {"action":"attest_artifact","file_id":"abc-123","artifact_name":"release-v2.1.tar.gz","metadata":{"version":"2.1.0"}} ``` Response: - `artifact_sha256`: SHA-256 of the attested file - `package_id`: unique attestation identifier - `attestation_file_id`: file ID of the saved attestation package (use this for verify_attestation) - `attestation_signed_url`: download URL for the attestation package JSON ### `verify_attestation` Verify a previously issued attestation package against the original artifact. Both must be in file storage. If verifying a package received from someone else, upload it first using the File Management tool. Required: - `file_id` (string): file ID of the original artifact - `attestation_file_id` (string): file ID of the attestation package JSON (from attest_artifact, or uploaded via File Management) Optional: - `check_bundle` (boolean, default true): verify CAB certificate bundle integrity ```json {"action":"verify_attestation","file_id":"abc-123","attestation_file_id":"def-456"} ``` Response: - `accept`: true if all checks pass - `failed_checks`: list of check names that failed (empty when accepted) - `manifest_sha256`: hash of the canonical manifest - `signer_public_key_hex`: the public key that signed the manifest ### `get_public_key` Return the signer's public key and algorithm info for independent verification. ```json {"action":"get_public_key"} ``` ## Typical Workflow 1. Upload a file using the File Management tool (`upload_standard`) to get a `file_id` 2. Call `attest_artifact` with the `file_id` — save the returned `attestation_file_id` 3. To verify later, call `verify_attestation` with both `file_id` (original artifact) and `attestation_file_id` (the attestation package) 4. Share the attestation package (downloadable via `attestation_signed_url`) with anyone who needs to verify independently ## Independent Offline Verification Recipients can verify attestation packages offline without this tool: https://github.com/Abraxas1010/verified-pqc-verifier ## Security Properties - **Post-quantum security**: ML-DSA-65 (FIPS 204 / Dilithium3) resistant to quantum attacks - **Hardware key protection**: signing key never leaves the hardware security module - **Tamper evidence**: any modification invalidates the signature - **Self-verification**: every attestation is verified immediately after signing ### Additional Product Content ## How It Works Upload a file and receive a cryptographic attestation package that mathematically proves what the file contained at the moment it was signed. The attestation binds your file's SHA-256 hash, a timestamp, and any metadata you provide into a signed manifest using ML-DSA-65 (Dilithium3 / FIPS 204). ## Formally Verified Acceptance Kernel Unlike conventional code-signing tools where the verification logic is tested but not proven, every attestation includes a Carried Algebraic Bundle (CAB) whose acceptance kernel has been formally verified in Lean 4. The verification logic is mathematically proven correct — not just tested against known inputs. The kernel includes a verified C implementation extracted directly from the Lean 4 proof source. ## Proof-Carrying Certificate Bundles Each attestation package contains a CAB bundle that cryptographically binds three elements into a single tamper-evident envelope: the artifact hash, the proof commitment, and the manifest signature. The bundle includes a Merkle tree over all verification artifacts (kernel source, provenance metadata, and expected outputs), ensuring that any modification to any component is detectable. ## 4-Check Verification Pipeline Every verification — whether through the hosted API or the standalone offline verifier — runs four independent checks that must all pass for acceptance: 1. **Signature validity** — the ML-DSA-65 signature over the canonical manifest is cryptographically correct 2. **Manifest consistency** — the package ID matches the SHA-256 of the canonical manifest bytes 3. **Artifact integrity** — the file's SHA-256 matches what was recorded in the signed manifest 4. **CAB certificate integrity** — the Merkle tree over all bundle artifacts verifies against the committed root ## NIST PQC Parameter Coverage The underlying VerifiedPQC protocol stack supports all 6 NIST post-quantum parameter sets: ML-KEM-512, ML-KEM-768, ML-KEM-1024 for key encapsulation, and ML-DSA-44, ML-DSA-65, ML-DSA-87 for digital signatures. The attestation service uses ML-DSA-65 (security level 3) for signing, backed by PQClean reference implementations — real, audited, standardized byte-level runtimes, not toy cryptography. ## Hardware Key Protection The ML-DSA-65 signing key is provisioned inside a Google Cloud KMS hardware security module. The private key never leaves the HSM — signing requests are sent to KMS, which returns the signature. Even if the service infrastructure were fully compromised, the signing key cannot be extracted. Every signing operation is logged by Google Cloud for audit purposes. ## Security Foundations The security model draws on information-theoretic foundations including privacy amplification and the leftover hash lemma. Constructive hardness guarantees are backed by contextuality-based impossibility proofs for the underlying lattice assumptions. These are not just computational security claims — the protocol stack includes formally verified components with mathematical correctness proofs. ## Independent Verification Attestation certificates can be verified without any connection to this service. The open-source standalone verifier is available at [github.com/Abraxas1010/verified-pqc-verifier](https://github.com/Abraxas1010/verified-pqc-verifier). It includes the ML-DSA-65 verification binary, the trust anchor with the issuer's public key, and a step-by-step guide. No account, API access, or trust in our servers is required. The cryptographic proof is self-contained. ## Independent Audit An independent operational audit (2026-03-28) confirmed the full protocol stack: runtime replay correctness, byte-level transport verification, mutation rejection, cross-backend interoperability, fuzz rejection, policy scenario enforcement, and performance envelope compliance across all supported parameter sets. ### Frequently Asked Questions #### How do I connect this tool to an external agent? - Page URL: https://www.agentpmt.com/faq - Markdown URL: https://www.agentpmt.com/faq?format=agent-md You can install the local MCP server by opening a terminal and running: ``` npm install -g @agentpmt/mcp-router agentpmt-setup ``` This will connect you to local agents like Claude Code, Windsurf, Grok Build, Cursor, etc. Alternatively you can connect to the hosted version with this config block, no installation required: ``` { "mcpServers": { "agentpmt": { "type": "streamable-http", "url": "https://api.agentpmt.com/mcp", "headers": { "Authorization": "Bearer ", "x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}" } } } } ``` [View MCP Connection Instructions](/docs/mcp-reference/connection) for more details. #### How does an external agent use this tool? - Page URL: https://www.agentpmt.com/faq - Markdown URL: https://www.agentpmt.com/faq?format=agent-md After the external agent is connected to an Agent Group that can use this tool, paste this prompt into the agent: > Use the AgentPMT-Tool-Search-and-Execution tool. First call action 'get\_instructions' so you know how to use the tool search interface. Then call action 'get\_schema' with tool\_id 69c99cefc3ba2714db75e12a ("Quantum-Safe File Attestation"). After reading the schema and any returned instructions, tell me what this tool can do, we are going to be using it The agent should fetch the tool schema first, collect the required parameters for your request, and then call the tool through AgentPMT. ### Dependencies This product has no public dependency products.