Apply as Issuer

What is an Issuer?

Issuers make cryptographically signed assertions about media artifacts (videos, images, audio, documents).

• ISSUED_BY - "We published this artifact"
• NOT_ISSUED_BY - "This artifact is not ours"
• DISPUTE - "We dispute an existing assertion on this artifact"
• INTENT - "This is parody / training / marketing"
• METHOD - "AI-generated / human-created / hybrid"

MIR records who made each assertion. MIR does not verify accuracy.

How It Works

Every assertion is signed with your private key before submission. MIR uses your public key to verify the signature came from you.

• Browser Signer - Generate a key pair and sign assertions directly in the portal. No code required.
• API Integration - For automated workflows, generate an ECDSA P-256 (ES256) key pair, register the public key with MIR, and sign assertion payloads with your private key before calling the API.

Your private key never leaves your control. MIR only stores your public key.

Assertions are tied to the content itself, not where it's hosted. When your media is shared or embedded on other sites, the MIR badge follows it — anyone can verify the original issuer regardless of where the file appears.

A subscription is required to create assertions. You can test the signing flow on the Signer page before subscribing.