Integration Surfaces
All the ways you can connect to NexArt: API, verifier, CLI, n8n, and SDKs.
Overview
NexArt can be accessed through several surfaces depending on your use case. This page lists them all in one place.
Node API
The primary integration point for most builders. Two endpoints are available:
- POST /v1/cer/ai/certify creates a CER (
bundleType: "cer.ai.execution.v1"), attests it, and returns a signed receipt with a verification URL. Recommended for most integrations. - POST /v1/cer/ai/create creates a CER bundle without attestation. Useful if you want the bundle for your own records or plan to attest it separately.
Authentication uses an API key passed as a Bearer token (NEXART_API_KEY).
Public Verifier
verify.nexart.io is the public verification portal. Anyone can verify a record by:
- Execution ID:
https://verify.nexart.io/e/exec_abc123 - Certificate hash:
https://verify.nexart.io/c/sha256%3A7f83...
The verifier uses a redacted, public-safe representation of the record. Sensitive input and output content is not exposed. Verification checks bundle integrity, node signature, and receipt consistency.
Attestation Node
The attestation node signs CERs and issues receipts. Its public surfaces are:
- node.nexart.io shows the node's identity and status.
node.nexart.io/.well-known/nexart-node.jsonpublishes Ed25519 signing keys (usingkidandactiveKidfields) for independent verification.
n8n Integration
The NexArt n8n community node allows you to certify AI execution results inside n8n workflows. The node calls POST /v1/cer/ai/certify and returns a verificationUrl that can be stored or shared.
NexArt CLI
The command-line interface for creating, certifying, and verifying CERs, plus deterministic rendering. As of v0.7.0, nexart ai verify accepts both raw CER bundles and CER packages.
Install and run with:
npx @nexart/cli --helpSDKs
- AI Execution SDK for CER creation and attestation workflows.
- CodeMode SDK for deterministic generative execution.
- UI Renderer SDK for deterministic UI rendering.