For AI companies. Your legal shield for generative content.
Every AI-generated face, voice, or brand is a potential lawsuit. PRE-GEN gives you cryptographic proof of authorization before the first pixel is produced — turning legal risk into a verifiable record.
The legal problem is real — and growing.
Right of publicity lawsuits, GDPR complaints, EU AI Act obligations, class-action deepfake claims — the legal surface of generative AI is expanding faster than any policy team can cover. And it's not just faces anymore. Voices, artistic styles, brand identities, 3D models, typefaces, product designs — anything your model can reproduce is a potential claim.
PRE-GEN replaces guesswork with evidence. A single API call returns a cryptographically signed decision — and that signature is your proof that the content was authorized by the rights-holder themselves.
What you actually get.
Every allow-decision carries a signed license with the rights-holder's own cryptographic key. When a complaint arrives, your answer is an evidence bundle that any court, regulator, or third party can verify independently — not an internal debate about what the model was "supposed to do."
Regulators are demanding authorization, attribution, and audit trails for synthetic content. PG's append-only hash-chained log with external anchoring produces exactly the evidence record that the EU AI Act, GDPR, CCPA, and US right-of-publicity laws are starting to require. Integrate now, not after the first enforcement action.
Brand campaigns, celebrity endorsements, estate-authorized depictions — high-value use cases that your safety filters refuse by default because there's no way to verify authorization. PG gives the model a clean, verifiable way to say "yes, this one is authorized" — and charge premium rates for it.
A verification round-trip fits into existing inference pipelines without UI changes, SDK modifications, or prompt engineering. Server-to-server, before generation — your users never see it.
Licenses can carry machine-readable generation guidelines: color palettes, typography rules, 3D mesh references, style parameters, brand usage instructions. Your model gets both authorization and a specification of how the content should look — producing output that's not only legal but correct.
Apache-2.0 licensed, no privileged operator, federated architecture with cross-signing registries. Integrate once — not per-vendor, not per-jurisdiction.
How it fits into your pipeline.
When a user sends a prompt, the provider detects whether it references a registered subject, then issues a server-to-server query to the registry. The registry evaluates opt-outs, license status, scope, and extensions — returning a signed decision.
Integration example.
A single server-to-server call before generation. No SDK required.
// Pre-generation verification — server-side // Call this before generating any content depicting a subject const response = await fetch('https://registry.prampta.com/v1/verify', { method: 'POST', headers: { 'Content-Type': 'application/json', 'Authorization': 'Bearer ' + PROVIDER_TOKEN, }, body: JSON.stringify({ provider_id: 'your-provider-id', licensee_id: 'licensee-account-id', subject_id: 'subject-id-or-null', prompt: userPrompt, model: 'your-model-name', modality: 'image', intended_use: { channel: 'social', product: 'campaign-spring-2026', } }) }); const decision = await response.json(); // decision.allowed — boolean // decision.code — PG_ALLOWED | PG_SUBJECT_OPTED_OUT | ... // decision.obligations — required disclosures, labels // decision.decision_id — unique, for audit trail if (decision.allowed) { generateContent(userPrompt, decision); } else { refuseGeneration(decision.code); }
Unknown rules are enforced by refusal, never by skip. If the verifier doesn't understand a license term, it does not pass.