# NexArt

> Verifiable AI execution infrastructure: Certified Execution Records, signed receipts, and independent verification.

## Core pages

- [Homepage](https://nexart.io/): Prove what your AI actually ran. NexArt seals every execution into a Certified Execution Record. Tamper-evident, cryptographically signed, i
- [How NexArt Works](https://nexart.io/how-it-works): NexArt creates verifiable records of AI execution that can be independently checked. Five steps from execution to proof.
- [Pricing: Certification Plans and API Access](https://nexart.io/pricing): Running AI is easy. Defending it later is the hard part. NexArt pricing gives you independently verifiable execution evidence. Compare Free,
- [NexArt Protocol: Open Execution Verification Standard](https://nexart.io/protocol): The NexArt Protocol defines how AI executions are captured, sealed, and independently verified. An open standard for deterministic and tampe
- [Security Architecture: Runtime Isolation, Hashing, and Audit Controls](https://nexart.io/security): How NexArt enforces isolated, deterministic, and auditable AI execution. Runtime sandboxing, SHA-256 hashing, minimal retention, signed atte
- [Certified Execution Records (CERs): What They Are and How They Work](https://nexart.io/certified-execution-records): CERs replace opaque AI logs with tamper-evident, cryptographically sealed proof of execution. Inputs, outputs, and context bound into a sing
- [Deterministic Execution Records: Canonicalization and Hash Guarantees](https://nexart.io/determinism): How NexArt produces deterministic execution records. Canonical field ordering, stable SHA-256 certificate hashes, and versioned guarantees e
- [Modes: Protocol Execution Surfaces](https://nexart.io/modes): NexArt modes are protocol surfaces for authoring deterministic generative systems. SoundArt, Code Mode, Shapes, and Noise are protocol-enfor
- [Auditable AI Execution: Standards Alignment for ISO 42001, SOC 2, NIST](https://nexart.io/reference/standards): How Certified Execution Records and signed attestation receipts map to evidence requirements for ISO/IEC 42001, SOC 2, and NIST AI RMF. Audi
- [Glossary: NexArt Protocol and CER Terminology](https://nexart.io/glossary): Definitions for Certified Execution Records (CER), certificateHash, attestation nodes, deterministic execution, context signals, and all key

## Comparisons

- [Logs vs Certified Execution Records](https://nexart.io/comparisons/logs-vs-certified-execution-records): Logs track what happened. Certified Execution Records prove it. A comparison of observability logs and cryptographically verifiable executio
- [Audit Trails vs Verifiable Execution](https://nexart.io/comparisons/audit-trails-vs-verifiable-execution): Audit trails track access and changes. Verifiable execution proves what AI systems produced. A comparison for compliance and risk teams.

## Use cases

- [Execution Integrity for AI Agents](https://nexart.io/use-cases/ai-agents): AI agents make decisions and invoke tools autonomously. NexArt provides tamper-evident, independently verifiable execution records for every
- [Execution Evidence for Regulated AI Workflows](https://nexart.io/use-cases/regulated-workflows): Regulated industries need tamper-evident execution evidence. NexArt produces Certified Execution Records that satisfy audit, compliance, and
- [Verifiable Evidence for Governed AI Decisions](https://nexart.io/use-cases/governed-decisions): Governance defines what AI systems should do. NexArt proves what they actually did. Certified Execution Records provide the evidence layer g
- [Financial Services: Verifiable AI for Regulated Finance](https://nexart.io/use-cases/financial-services): Verifiable AI execution for financial services: model decisions, credit assessments, fraud signals, and trading workflows with audit-grade C
- [AI Evaluation: Verifiable Eval Pipelines](https://nexart.io/use-cases/ai-evaluation): Verifiable execution for AI evaluation pipelines. Reproducible eval runs with tamper-evident Certified Execution Records for benchmarks, reg

## Developer

- [Quickstart: NexArt SDK & CLI](https://nexart.io/builders/quickstart): Get your first certified run in under 5 minutes. Install the CLI, authenticate, run a sketch, and verify the snapshot.
- [CLI Reference: NexArt Builders](https://nexart.io/builders/cli): NexArt CLI reference for command-line certification, verification, and execution record management.
- [Builder Certification: NexArt](https://nexart.io/builders/certification): Certification path for builders integrating NexArt verifiable execution into AI systems and workflows.
- [API Overview: NexArt](https://nexart.io/docs/api/overview): Overview of the NexArt API for programmatic CER creation and certification. REST endpoints for AI execution certification.
- [Certification API: NexArt Docs](https://nexart.io/docs/api/certification): REST API reference for the NexArt certification endpoint. Submit execution evidence and receive a signed Certified Execution Record.
- [AI CER Creation Endpoint: NexArt](https://nexart.io/docs/api/ai-cer-creation): REST endpoint for programmatic AI CER creation. Submit execution snapshots and receive tamper-evident Certified Execution Records.

## Blog

- [The Execution Evidence Layer: Where NexArt Fits in the AI Stack](https://nexart.io/blog/execution-evidence-layer-where-nexart-fits): Where does NexArt fit in the AI stack? This guide explains the execution evidence layer and why Certified Execution Records are different fr
- [When a Client Challenges Your AI Output, Will Logs Be Enough?](https://nexart.io/blog/client-challenges-ai-output-logs-not-enough): For small AI companies, the real pressure is not only regulation. It is what happens when a client says your system got it wrong and asks yo
- [OpenTelemetry vs Verifiable Execution: Why Logs and Traces Aren’t Enough for AI Systems](https://nexart.io/blog/opentelemetry-vs-verifiable-execution): OpenTelemetry vs verifiable execution: what logs, traces, and telemetry solve, where they stop, and why AI systems increasingly need a stron
- [The Missing Proof Layer in AI: Verifiable Execution Infrastructure](https://nexart.io/blog/verifiable-execution-infrastructure): What is verifiable execution infrastructure? A Medium-ready guide to the emerging AI infrastructure layer focused on structured execution ar
- [Your AI Made a Decision. Can You Prove the Workflow That Produced It?](https://nexart.io/blog/prove-workflow-that-produced-it): A Medium-optimised deep dive on why AI logs are not enough for multi-step workflows, and how NexArt extends Certified Execution Records with
- [How NexArt Protects AI Execution Evidence From Tampering](https://nexart.io/blog/how-nexart-protects-execution-evidence): Learn how NexArt's Certified Execution Records create tamper-evident, independently verifiable AI execution evidence, and how hardware-backe
- [How to Add Verifiable Execution to LangChain and n8n Workflows (with NexArt)](https://nexart.io/blog/verifiable-execution-langchain-n8n): Most AI workflow tooling helps you run chains, agents, and automations. Very little helps you prove what actually ran later. This article wa
- [What Is the AI Execution Integrity Framework (AIEF) — And Why AI Systems Need It Now](https://nexart.io/blog/what-is-aief): There is no widely adopted standard that defines what verifiable AI execution means in practice. The AI Execution Integrity Framework (AIEF)
- [What to Build in 2026: High-Risk AI Businesses That Win Under the EU AI Act](https://nexart.io/blog/high-risk-ai-businesses-eu-ai-act): The EU AI Act creates a new category of compliance-native AI businesses. This article explores the high-risk SaaS opportunities emerging in 
- [EU AI Act 2026 Checklist: Are Your High-Risk AI Systems Actually Audit-Ready?](https://nexart.io/blog/eu-ai-act-2026-checklist): With the EU AI Act high-risk obligations taking effect in August 2026, many teams are discovering that traditional logs may fall short for t
- [How to Add Verifiable Execution to an AI Agent in Under 30 Minutes](https://nexart.io/blog/how-to-add-verifiable-execution-to-ai-agent): Most agent systems rely on logs for accountability, but logs are not proof. This guide walks through adding Certified Execution Records to a
- [Why We Built verify.nexart.io](https://nexart.io/blog/why-we-built-verify-nexart-io): Most AI systems do not provide a clean way to independently verify what actually ran. verify.nexart.io is a public verification surface for 
- [Verifiable AI Execution vs zkML: What NexArt Proves, What It Doesn't, and How Privacy Works in Practice](https://nexart.io/blog/verifiable-ai-execution-vs-zkml): NexArt and zkML both fall under 'verifiable AI,' but they solve different trust problems. This article clarifies the distinction between exe
- [AI Auditability and the EU AI Act: Why Execution Evidence Matters](https://nexart.io/blog/ai-auditability-eu-ai-act): The EU AI Act requires auditable AI systems, but most are built for observability, not auditability. This article explains why execution evi
- [AI Audit Trails vs Verifiable Execution](https://nexart.io/blog/ai-audit-trails-vs-verifiable-execution): Audit trails provide visibility, but visibility is not proof. This article explores the gap between tracking behavior and proving execution,
- [Execution Drift in AI Systems (and Why It Matters More Than You Think)](https://nexart.io/blog/execution-drift-in-ai-systems): Two executions with the same inputs can produce different results. Execution drift is not a bug; it is a property of modern AI systems. The 
- [What Is a Certified Execution Record (CER)?](https://nexart.io/blog/what-is-a-certified-execution-record): Most AI systems produce logs, but logs are not proof. A Certified Execution Record is a cryptographically verifiable artifact that turns exe
- [How to Verify AI Execution (and Why Logs Are Not Enough)](https://nexart.io/blog/how-to-verify-ai-execution): Most AI systems rely on logs for accountability, but logs are not proof. This article explores why verification requires a different model, 
- [The Missing Layer in AI Systems: Verifiable Execution](https://nexart.io/blog/verifiable-ai-execution): Most AI systems produce logs that are mutable, incomplete, or opaque. Certified Execution Records replace them with tamper-evident, cryptogr

## Related sites

- [Documentation](https://docs.nexart.io/llms.txt)
- [Verification portal](https://verify.nexart.io)