Axia Sign

Embed cryptographic provenance at the moment of creation.

What it is

Axia Sign is the entry point to the trust layer. It hashes content, signs it with a publisher-bound Ed25519 key, anchors the leaf in the public Axia Log and (optionally) emits a C2PA-compatible manifest — in a single API call. For media captured on a device, Trusted Capture binds the asset to a hardware-attested device at the moment of recording (axia.capture.v1).

How it works

Hash

SHA-256 fingerprint computed client-side or server-side. The raw bytes never need to leave your environment.

Sign

Ed25519 signature bound to a registered, DNS-verified identity. Key lifecycle (rotation, revocation, BYOK) is enforced.

Anchor

The signed leaf is appended to the Axia Log Merkle tree and returned as a verifiable receipt.

Capture (optional)

Bind media to the device that recorded it via Apple App Attest, Android Play Integrity or WebAuthn. Receipts then carry the device origin alongside the publisher identity.

What you get

• SHA-256 content fingerprint
• Ed25519 signature bound to your identity
• Merkle leaf inclusion in Axia Log
• Optional C2PA manifest
• Public verification URL (/r/:id)
• Conformant axia.receipt.v1 receipt
• Optional axia.capture.v1 device-origin envelope

Pairs with…