AI execution evidence
NexArt turns an AI execution into a Certified Execution Record: portable, cryptographically sealed, independently verifiable evidence of what ran, on which inputs, by which system.
For engineers
One SDK call. No middleware, no proxy, no infrastructure change.
For auditors
Evidence that verifies independently, without trusting the operator.
Cryptographically sealed · Externally timestamped · Publicly verifiable
Why evidence is needed
Logs can be edited, deleted or reconstructed. Inputs, parameters and outputs are often stored separately. That may support debugging, but it does not give an external reviewer independent evidence of what happened.
Customer dispute
A customer challenges an AI-generated decision or action.
Audit request
An auditor asks for evidence tied to the original execution.
Incident investigation
Your team must establish exactly what the system received and returned.
Regulated workflow
A material AI decision requires defensible execution-level records.
Certified Execution Records
A lightweight SDK records the selected inputs, parameters, outputs and execution context at runtime. It seals them into a tamper-evident artifact called a Certified Execution Record.
The NexArt attestation node checks and signs the record. Any third party with access to the record can independently verify its integrity using the record, the signature and the node’s public key.
How it works
Three distinct layers with distinct trust boundaries. Each can be adopted independently.
Execute
The SDK creates the record inside your environment.
Local creation · No certification fee · No infrastructure change
Certify
The NexArt attestation node checks and signs the record.
Attestation signature · Optional external timestamp · Defensible evidence
Verify
A third party recomputes the record hash and checks the signature.
No account · No API key · No dependency on NexArt-side data
In production
When a buyer accepts terms on HAGGIN, NexArt seals the acceptance: a public, timestamped record that holds a fingerprint of the terms, never the terms themselves. Either side can verify it, no account needed. Change one comma and the fingerprint stops matching.
See how HAGGIN uses itConfidential execution
NexArt can replace raw inputs and outputs in the record with cryptographic commitments. Sensitive prompts, customer data and model outputs remain within the organisation while the integrity of the execution can still be independently verified.
Explore Confidential ExecutionWhere it holds up
AI agent actions
Preserve verifiable evidence of the inputs, recorded tool calls and resulting actions across an agent workflow.
See AI agent evidenceCustomer-facing decisions
Respond to challenges involving lending, insurance, eligibility, pricing or recommendations.
Explore decision disputesApproval and policy workflows
Demonstrate which inputs, parameters and policy context were associated with a decision.
See policy workflow evidenceAI incident review
Preserve execution evidence before systems, models or logs change.
Review incident use casesAudit and assurance
Give reviewers a portable artifact they can inspect independently.
Explore audit evidenceMulti-step workflows
Group related execution records into one Project Bundle covering an agent session or business process.
Understand Project BundlesEvidence, not observability
Logs and observability
NexArt execution evidence
NexArt complements observability rather than replacing it. Keep your traces and logs for operations. Add NexArt where you need portable proof.
What verification proves
NexArt proves
The record proves the integrity of what was captured. The reliability of capture depends on how the integration and execution environment are controlled.
NexArt does not prove
Hosted verification
Use verify.nexart.io for simple public verification. No account or login is required. This hosted path requires the verification service to be available.
Independent verification
Use the CLI, SDK or standard cryptographic libraries with the record and relevant public key. No NexArt account or live NexArt service is required.
npx @nexart/cli verify record.cer.jsonimport { verify } from '@nexart/ai-execution'
verify(bundle)Framework alignment
Supports evidence and record-keeping activities relevant to frameworks including the EU AI Act, ISO/IEC 42001, SOC 2 and NIST AI RMF. NexArt does not itself make a system compliant.
Get started
Start with one AI call. Produce a verifiable execution record, certify it through an attestation node and give reviewers a verification path that does not depend on your internal logs.
Free to create. Paid to certify. Public to verify.
Stay close
New articles, protocol updates, and product notes. No spam, no fluff.