Feature · attestations
Every compliance claim becomes a cryptographic artifact.
How it works
Attestry anchors each claim to a SHA-256 hash with a stable revocation status, checkable on the public verification portal. EU AI Act Annex IV technical files go further: Ed25519-signed by Attestry and independently verifiable offline with only the public key — no Attestry round-trip on that path. Revocation status stays queryable, so historical proofs remain checkable.
Code sample
// Verify any Attestry attestation against the public API.
// Every certificate is fetchable by its SHA-256 hash —
// no SDK or auth required.
const certHash =
"a4f6e8d2c1b9e7f5a3d2b1c8e6f4a2d1" +
"b9e8f7c6a5d4b3c2e1f0a9b8c7d6e5f4";
const res = await fetch(
`https://attestry.ai/api/v1/verify/${certHash}`,
);
const { data } = await res.json();
// data = {
// valid: true,
// status: "active",
// frameworks: ["eu-ai-act", "nist-ai-rmf"],
// riskLevel: "high",
// issuedAt: "2026-04-12T14:00:00Z",
// expiresAt: "2027-04-12T14:00:00Z",
// organizationName: "Acme Compliance Co.",
// systemName: "Example Credit Scorer",
// hasZkProof: false,
// }Free plan includes fingerprinting, unverified attestations, and a public registry listing. Upgrade when you need signed proofs or SLA-backed verification.