The permission-first AI declarationv2.0 · 2026

Permission should be an API.

Every intentional AI use of a known creative asset should be able to ask, accept terms, and leave proof — in one call.

Registered literary work · TXu002501544 · no government endorsement implied

Live proof · one endpoint
POST /v1/clearance
Asset
Tidal Marsh at 05:42
purposegenerationcommercialtruebudget$20.00

One call returns a decision, price, obligations, policy evidence, and a signed receipt.

The rationale

AI made creation instant. Permission stayed fragmented.

01

The gap

Licenses, identity, price, and usage context live in different systems — if they exist at all.

02

The failure

A model can generate in seconds while a human clearance process can take days, weeks, or never finish.

03

The move

Put a narrow policy-decision gateway between intent and use. Make uncertainty explicit.

04

The proof

Return ALLOW, DENY, or REVIEW with terms and a signed, portable evidence receipt.

Simple by design

One decision surface. Many policy sources.

IPRS Clear does not replace licensing standards. It composes their answers with identity, intended use, and budget into a decision an application can act on.

RSL
license + payment terms
ODRL
policy expressions
Catalog
ownership + identity
Context
use + budget
ALLOW
DENY
REVIEW

RSL-compatible orchestration · ODRL-aware · source-preserving

Inspect the one-call contract
Six commitments

The declaration

01

Declare the asset

Known creative inputs should be named, not hidden in a workflow.

02

Ask before use

Permission belongs before generation or training, not after a dispute.

03

Show the terms

Price, attribution, and participation should be legible before acceptance.

04

Respect uncertainty

Missing or conflicting authority resolves to REVIEW, never silent permission.

05

Leave proof

Every decision should create portable evidence of what was asked and answered.

06

Build on open work

RSL and ODRL are inputs to orchestrate, not standards to rename.

Open thesis. Open contract. Managed trust.

The paper, API contract, and reference logic are designed to be inspectable. The business is the dependable hosted layer: identity, policy normalization, signed receipts, audit, security, and support.

Design partner offer
100 assets. 30 days.

Integrate one workflow, measure review reduction, and publish an evidence-backed case study when both sides agree.

Configure your first policy