For content platforms · For AI labs
The trust layer for
AI content licensing.
Content platforms hash each asset, choose what rights are granted for what AI use, and we sign the result as a verifiable licence (a W3C Verifiable Credential). AI labs verify it offline in milliseconds. One signing key, one trust anchor, the entire machine-readable rights stack.
W3C Verifiable Credentials · JWT-VC · Ed25519 · CoMP v1.0 compatible
- Signed by a neutral third party Not the issuer. Not the lab.
- Offline-verifiable in milliseconds No network call per asset.
- Free for AI labs · metered for platforms Verification is free. Issuance is paid.
Two crises, one missing layer.
For content platforms
Your catalog is full of creator-uploaded material with terms that are silent or inconsistent on AI training. When a creator sues because an AI lab trained on their work, you have nothing to defend yourself with except your existing T&Cs — which were never built for AI.
For AI labs
You're ingesting training data at scale with mounting pressure from the EU AI Act, state-level provenance laws, and private litigation. You need to verify rights programmatically, across millions of inputs, without slowing your pipeline. Bilateral deals don't scale.
Who fills the gap
We're not an AI lab. We're not a content platform. We're the third party that signs what issuers grant and that labs verify — with no business that competes with either side. That's the structural difference between us and self-signed credentials, coalition-controlled trust lists, or lab-built verification stacks.
What we do.
We sign verifiable rights licences for your content. The licence travels alongside the asset; AI labs verify it before they train.
Your platform sends us a hash
Your pipeline computes the SHA-256 of an asset locally and posts it to our API along with the rights you grant. The file never touches our infrastructure.
We sign a verifiable licence
Ed25519 signature, JWT-VC format, W3C-aligned. Carries the seven first-class rights (train, RAG, embed, display, eval, derive, commercial) and the scope conditions you specify.
The licence travels with the asset
You ship it however you already ship metadata — HTTP header, sidecar JSON, C2PA embed, marketplace API response. Same licence, multiple transports.
AI labs verify offline
Their training pipeline calls our SDK (`@licensefoundry/sdk` or `licensefoundry` Python). Signature check + revocation lookup runs in milliseconds, against a cached JWKS. Free.
Built for both sides.
For content platforms
Issue licences at scale. We handle verification.
- Per-asset rights licences issued at scale
- Bulk-import tooling to migrate existing catalogs
- Rights templates per content category
- Onchain anchoring + immutable audit trail
- Revocations not billed — trust infrastructure
For AI labs & downstream products
Verify rights before you train. Free SDK, offline by design.
- Offline SDK verification against cached JWKS — milliseconds per asset
- No API key for the default path — keyless, free, unmetered
- One trust anchor, every issuer under our DID
- MCP server for agent-native ingestion pipelines
- Audited Provenance subscription for marketable third-party attestation
Independent by design.
Independence isn't marketing — it's a structural property of who can credibly sign what. Self-signed credentials are an issuer's claim, not evidence. Coalition-controlled trust lists carry their members' biases. Robots.txt and C2PA address adjacent problems — opt-out and provenance — but not licensing. Bilateral lab-platform deals work for the giants and leave the mid-market exposed. A third-party signature from an entity with no business in either direction is the baseline this market is structurally missing.
Neutral signing
Not the issuer. Not the verifier.
Issuers can't sign their own credentials and call them verifiable — self-attestation is the model labs already reject. We sign for them, with our key, under our DID. The credential carries weight precisely because we have no incentive to lie about what was granted.
No conflict of interest
We don't train. We don't sell content.
We're not in either side's business. We have no incentive to declare more content trainable than it is, or fewer credentials valid than they are. Our only product is keeping the trust layer working for both sides — which fails the moment we tilt toward either one.
Audit-grade attestation
Third-party signature, by structure.
Regulators and external counsel give more weight to independent third-party attestation than to self-signed documents. A compliance report citing our DID is structurally more defensible than the same artefact a customer produced about itself.
More than compliance. A commercial advantage.
The defensive case is straightforward — when regulators or counsel ask, you have signed evidence. The commercial case is what most prospects miss: credentials change what each side can sell and what they can charge for. The same artefact that protects you when something goes wrong also widens the deal you can sign when things go right.
For content platforms
Charge a premium for credentialed catalogs.
A licensed dataset that ships with a signed credential trail is worth materially more to an AI lab than the same dataset on a "trust us" basis. Labs pay more for training data they can defend — and you're the one selling them that defensibility. The same credentials also win bilateral deals against competitors who can only offer their own assertion. Same catalog, higher take rate.
For AI labs
Sell certainty to your enterprise customers.
When your enterprise customers' procurement teams ask "what was this model trained on, and was it cleared?", today your answer is "trust us." With a credentialed training corpus, your answer is a signed report from an independent third party — verifiable by their legal team without trusting either of us. That converts the conversation from defending an objection to justifying a premium tier.
Compliance protects the floor of the business. Credentialed inputs raise the ceiling — for issuers, by widening what their catalog is worth; for labs, by letting them charge enterprise customers a premium for provable provenance.
Platform pricing. Simple and metered.
Pay for what you issue. Revocations are not billed — they're trust infrastructure. Pricing changes carry 90 days' notice to active accounts.
Explorer
Free/no card required
- 100 licences / month
- Unlimited offline verifications
- 25 onchain anchors
- Sandbox + production access
Growth
$499/month
- 3,000 licences / month
- Unlimited offline verifications
- 500 onchain anchors
- Webhooks · 24h SLA
Enterprise
Custom/contract
- Custom quotas + bundle pricing
- Negotiated SLA — commitment levels on request
- Dedicated tenant · private namespace · indemnity
- Multi-region · audit retention to 7 years
Per-asset bulk-migration fees apply when using the rights-collection tooling. Full pricing docs →
Lab pricing. Free by default.
Labs don't pay an issuer plan. The free Verify SDK is the default path. The Audited Provenance subscription activates when you're using credentialed training as a commercial signal — winning enterprise deals, satisfying procurement audits, backing compliance disclosures with independent attestation. Verification pricing is reviewed annually with 90 days' notice on any change.
Verify
Free/no key needed
- Offline SDK against cached JWKS
- Unlimited verification volume — no metering
- Milliseconds per check, in-process
- One trust anchor, every issuer under our DID
- 90 days' notice on any pricing change
Audited Provenance
$2,000/month
- Quarterly verification reports — 4 included per year
- "Audited-Corpus" attestation badge for customer-facing marketing
- Right to cite our DID + attestation in proposals + contracts
- Period audits + incident response at standard rates
- Everything in the free Verify tier
Enterprise
Custom/contract
- Unlimited compliance reports
- Regulator-response retainer included
- Indemnity tier — $25K–$100K / year
- Multi-jurisdictional support · multi-region
- Negotiated SLA — commitment levels on request
À la carte for labs that don't subscribe: $500 summary report / $5,000 period audit / $25,000 incident response. Online REST verification (for environments that can't cache JWKS) is metered from $0.001 / call. Full pricing docs →
Built on the standards that matter.
W3C VC Data Model 2.0
Standardised credential envelope
JWT-VC compact JWS
Wire format every JWT verifier handles
Ed25519 / EdDSA
Modern asymmetric signatures
CoMP v1.0 compatible
IAB Tech Lab standard for AI rights
Status List 2021
W3C revocation with offline cache
did:web
DNS-rooted trust anchor
Where the standards exist, we adopt them. Where they don't yet, our schema is designed to absorb the next version without breaking credentials we've already issued.
Start a 2-week pilot.
We're working with a small number of mid-market platforms and AI labs through 2026. If you're either, let's talk — first call is 40 minutes and you'll come away with a concrete sense of fit.
First call is 40 minutes. No deck required.