Pricing

Start by verifying. Pay when you scale.

Verification of the open C2PA ecosystem is free and useful on its own. You can confirm where signed content came from before you ever issue a credential. Sign and operate at volume when you're ready.

Free

$0forever

Verify the existing C2PA ecosystem with generous limits. No card.

Start verifying
  • Verify API + browser SDK
  • Full verdict model & AI disclosure
  • Provenance lookup by content hash
  • 1 signing identity
  • Community support
  • Workspace policies & review queue
  • Webhooks & SSO
Most popular

Team

$249per month

Sign at volume, route by policy, and bring a newsroom or product team along.

Start a Team trial
  • Everything in Free
  • High-volume verify & sign
  • Unlimited signing identities
  • Policy engine + review queue
  • Webhooks & transparency-log export
  • Role-based access control
  • Email support

Enterprise

Custom

Tenant isolation, custom trust lists, and assurances for regulated workflows.

Talk to us
  • Everything in Team
  • Custom trust lists & policies
  • SSO / SAML & SCIM
  • Dedicated isolation & data residency
  • Audit log retention
  • Security review & SLA
  • Priority support

Every tier returns the same honest verdict model. Higher tiers add scale, policy automation, and assurances, never a different definition of “verified”.

Questions

The fine print, in plain language.

Why does verification start free?

Because verification has standalone value. You can check content signed by the existing C2PA ecosystem (Adobe, OpenAI, cameras, and more) without ever issuing a credential of your own. Most teams adopt verification first and add signing later.

What counts as a verification or a signature?

A verification is one call to the verify endpoint or SDK. A signature is one credential issued through the sign endpoint. Provenance lookups by content hash against the transparency log are counted with verifications.

Do you retain the media I verify?

No. Verification works on the bytes you send and returns a verdict; we don't retain the asset to operate the product. The transparency log records credentials you choose to issue, by hash and manifest, not the media itself.

Is trust automatic for known issuers?

Never. Recognising a known issuer is a convenience so you can see who signed something. Whether a signer is trusted is always your workspace's policy decision. That's the line between “provenance present” and “verified”.

Get started

Verify your first asset in minutes.

Create a workspace, drop in a file or a hash, and get an honest verdict. Add signing identities whenever you're ready to issue credentials of your own.