Open Source

Open source infrastructure for verifiable AI systems

CertifiedData publishes the components that external systems need to integrate with, verify against, and build on — without requiring access to the core platform.

Three public repositories. Three distinct layers of the AI trust stack.

How the layers fit together

Each public repo exposes one layer of the stack. The core platform is private.

Layer	Repository	Role
Trust & verification	`certifieddata-public`	Verify that artifacts are real, unaltered, and certified
Agent Commerce	`certifieddata-agent-commerce-public`	Execute policy-governed payments and produce cryptographic receipts
Data safety	`pii-scan`	Detect PII in datasets before certification or training
Core platform	`certifieddata-platform (private)`	Generation, certification, registry, dashboard, and all product surfaces

Verification layer

`certifieddata-public`

Public

Verify certificates. Trust artifacts. Prove provenance.

The public verification and trust layer for the CertifiedData platform. Contains the verification SDK, certificate schema tools, and PII scanning integration. Use it to verify that a dataset or AI artifact was certified by CertifiedData — without needing a platform account.

What it includes

—Ed25519 certificate signature verification
—SHA-256 dataset hash validation
—Certificate schema tools and type definitions
—PII scanning integration (references pii-scan)
—Published public key at /.well-known/certifieddata-public-key.pem

View on GitHub →Verify a record Browse the registry

Agent Commerce layer

`certifieddata-agent-commerce-public`

Public

Execute. Settle. Prove it happened.

The public execution and settlement layer for Agent Commerce. Contains the OpenAPI contract, AsyncAPI event schema, payment SDKs, a mock server for local development, and test vectors. Use it to integrate AI agents with policy-governed, receipt-issued payment infrastructure.

What it includes

—OpenAPI contract for all Agent Commerce endpoints
—AsyncAPI event schema (authorization, settlement, receipt events)
—Python and TypeScript SDKs
—Mock server for local development without real payments
—Test vectors for Ed25519 receipt verification
—llms.txt for AI system discoverability

View on GitHub →Agent Commerce overview Verifiable agent transactions

Data safety utility

`pii-scan`

Public

Scan before you train. Know what's in your data.

A lightweight, standalone PII detection utility for datasets used in AI training pipelines. Identifies personal information across common data formats before datasets are certified or published. Integrates with the CertifiedData certification workflow.

What it includes

—PII pattern detection across CSV, JSON, and Parquet
—Configurable rule sets for GDPR, HIPAA, and custom patterns
—Pre-certification scan integration
—Zero external dependencies in core scanner
—Suitable for CI/CD pipeline integration

View on GitHub →Certification workflow

Why these components are public

—

Verification must be independent

A certificate is only trustworthy if it can be verified without relying on the platform that issued it. The verification SDK and public key are open so any system can confirm certificate integrity without a CertifiedData account.

—

Integration requires a contract

Developers building AI agents need a stable, versioned API contract and event schema before they can integrate. The Agent Commerce public repo provides that without requiring platform access or early sign-up.

—

Trust is built incrementally

Publishing the components that touch external systems — verification, execution, data safety — lets the community inspect and build confidence in the primitives before adopting the full platform.

Start building

Use the public repos to integrate, verify, and extend — then bring the full platform in when you need generation, certification, and the registry.

Agent Commerce →Verify a record How it works