Prepare identity
Reserve existing serials or generate UPIs before a batch, work order, or final assembly step.
Auth3D
Create product authentication records and digital certificates of authenticity inside the production process. Connect Auth3D directly, or let an authorized Codex or Claude Code agent coordinate identifiers, record evidence, production data, and permanent verification URLs.
Auth3D can sit beside an ERP, MES, QMS, label service, or custom production application. The factory keeps its operating system; Auth3D provides the permanent identity and customer-facing verification record.
Reserve existing serials or generate UPIs before a batch, work order, or final assembly step.
Register the individual object with its design, maker, image of record, and production context.
Encode the permanent record URL in a QR code, NFC/RFID workflow, label, or serial lookup.
Read the record back after each write and store its UPI and permanent URL in the production system.
Every connection can discover the authenticated manifest, OpenAPI request shapes, account context, available workflows, approval rules, and honest limits before it acts.
GET /api/v1/manifest
GET /api/v1/openapi.json
GET /api/v1/me
# Then use only the returned
# endpoints, rules, and limits.
The API is the Auth3D side of the connection. A direct integration or agent can exchange data with another platform only when it also has that platform's permission.
Carry work-order, product-family, customer, or batch references into the record workflow.
Create identifiers and records at the production milestone that makes sense for the line.
Place approved production facts and image evidence beside the permanent object identity.
Return the UPI and stable URL for QR, NFC, RFID, serial, packaging, or documentation output.
Auth3D records product identity, maker claims, design context, production information, and supporting evidence. It does not replace a regulator, test laboratory, or independent certification authority. External systems remain under their own credentials and controls.
Yes. An authorized production service or agent can reserve identifiers, create object records with image evidence, update production fields, and read the resulting permanent record back through API v1.
Yes. The API exposes an authenticated manifest and OpenAPI 3.1 contract so an authorized agent can discover available endpoints, request shapes, operating rules, and current limits before acting.
No. Auth3D creates owner-managed product authentication records and digital certificates of authenticity. It does not independently certify regulatory compliance, test results, or safety claims.
Auth3D provides the record API. A direct integration or authorized agent can coordinate Auth3D with another platform when it also has permission and credentials for that platform.
Create an account, open Integrations, and give each agent or production service its own revocable API connection.