Portable trust artifacts
The Anchor Card, AI BOM, Evidence Envelope, CertifiedArtifactBundle, and a public Agent Passport subset. Open schemas anyone can read, generate, and verify.
ClearPoint Open Anchor
Proof that an AI agent is what it claims to be.
Open Anchor is the public, open-standard layer of ClearPoint’s trust fabric. Portable trust artifacts and an open validator let anyone verify an agent’s certification status, validity, and revocation without exposing the evidence, secrets, or private policy behind it.
The public layer
An open standard, not a closed black box.
Anchor is ClearPoint’s trust fabric. Open Anchor publishes the artifact layer of it: the formats and the validator. The proof a buyer, partner, or auditor needs is something they can inspect for themselves.
An open CLI validator
The reference implementation and command-line validator are open source. Check any Anchor-compatible artifact against the published schemas and a public conformance suite, locally and with no account.
Dual-licensed, openly
Apache 2.0 covers the validator and reference code, including patent grant. CC BY 4.0 covers the schemas, protocol, and docs.
What verification proves
Least disclosure by default.
Public verification projects canonical Anchor state and nothing more. Raw evidence, prompts, secrets, customer data, and private policy logic never travel through it.
Certification status
The canonical Anchor state: certified, pending, failed, recertification required, revoked, or retired.
Validity window
Whether the certification is current, with an explicit expired flag rather than a guessed-at date.
Revocation
A live revocation check, so a pulled certification reads as pulled, not as still-good.
Digests, not contents
AI BOM and policy envelope are verified by digest. The proof is portable; the private detail stays put.
Evidence freshness
A summary of how recent the underlying evidence is without ever exposing the evidence itself.
Anchor-compatible is open.
Any implementation that validates against the published schemas and passes the public conformance suite can call itself Anchor-compatible. That’s the point of an open standard. The artifact layer belongs to everyone.
Anchor-Certified is issued.
Anchor-Certified is a retained ClearPoint Logic trademark. Only ClearPoint, or an authority we designate, issues the certified attestation. Compatible means the format checks out; certified means we stand behind the status.
Open vs. Pro
Public proof, private authority.
Open Anchor tells the world how to verify the artifacts. Anchor Pro is the Meridian fabric ClearPoint runs to issue, enforce, revoke, and audit those artifacts.
Open Anchor
Open Anchor is the public contract: schemas, artifact envelopes, validator behavior, public status fields, and the conformance suite. Anyone can test compatibility locally without an account or access to private evidence.
Anchor Pro
Anchor Pro is Meridian's proprietary trust fabric: certification authority, policy enforcement, private evidence retention, revocation workflows, and audit operations. Buyers get portable proof and exports without exposing the control logic behind the decision.
Where the line sits
The artifact layer is open. The authority is not.
We open the portable contract: schemas, artifact envelopes, validator behavior, public status fields, and compatibility tests. We keep the operational authority private: certification decisioning, policy evaluation internals, evidence graph, revocation operations, customer-specific controls, and enforcement workflows.
Pre-stable, on purpose
Open Anchor is a 0.x standard.
We’d rather publish the standard early and version it honestly than freeze it before it’s right. Open Anchor follows semantic versioning. During 0.x, schema changes ship with a deprecation notice, and 1.0 marks the stable, backward-compatible line. Tell us what you want to verify and we’ll keep you in the loop.