Skip to content

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ProofMeta License Contracts

Layer: License Depends on: proofmeta-primitive-core Guarantees: Chain-agnostic license semantics

License


The idea in 10 seconds

A license is just four things:

scope        → what you're allowed to do
terms        → the fine print (hashed, so it can't change silently)
pricing      → what it costs (or: free)
id           → a name to reference it by

That's it. One JSON object. Works for a beat, an API, a dataset, a model, a book — anything.

What a license looks like

{
  "id": "commercial-standard",
  "scope": ["commercial", "derivative-allowed", "ai-training-excluded"],
  "terms_url": "https://youragent.ai/terms/commercial",
  "terms_hash": "sha256:a1b2c3...",
  "pricing": {
    "model": "one-time",
    "amount": "5.00",
    "currency": "USD"
  }
}

An agent reads this and knows everything it needs:

  • ✅ Can I use this commercially? → yes (commercial)
  • ✅ Can I remix it? → yes (derivative-allowed)
  • ❌ Can I train on it? → no (ai-training-excluded)
  • 💰 What does it cost? → $5, one-time

No ambiguity. No lawyer needed. No chain required.

Pricing models

Model When to use Example
free Open access Community tools, open data
one-time Pay once, use forever Stock photos, beats, templates
subscription Recurring access SaaS APIs, premium feeds
usage-based Pay per use AI training data, per-request APIs

Ready-made templates

Don't want to write your own? Copy one:

Template Scope Pricing
free-attribution Non-commercial, derivatives OK, credit required Free
commercial-standard Commercial, derivatives OK, no AI training $5 one-time
commercial-no-ai Commercial, credit required, no AI training $10 one-time
ai-training-dataset Commercial, AI training OK, credit required $0.01/record
saas-api-access Commercial, sublicensable, revocable $29/month

How it fits together

┌─────────────────────────────┐
│  Execution Layer            │  ← Stripe, Solana, Lightning, IPFS
│  (how you pay & deliver)    │     chain-specific, pluggable
├─────────────────────────────┤
│  License Layer  ← you are here
│  (what you're allowed to do)│     chain-agnostic, universal
├─────────────────────────────┤
│  Primitive Layer            │  ← Signed Envelopes, DID, ed25519
│  (cryptographic proof)      │     the math
└─────────────────────────────┘

The License Layer never touches chains, payments, or delivery. It only answers: what are the rights, what are the terms, what's the price?

Everything else is a plugin.

Scope tags

Defined in primitive-core/docs/scope-vocabulary.md. The core set:

Tag Means
commercial Commercial use allowed
non-commercial Non-commercial only
derivative-allowed Remixes, adaptations OK
attribution-required Must give credit
ai-training-allowed ML training OK
ai-training-excluded No ML training
sublicense-allowed Can sub-license
revocable Provider can revoke

Need something custom? Use a URL: "https://youragent.ai/scope/eu-only"

Schemas

Why purchase intents + run receipts + ratings are in license-contracts

They define chain-agnostic contract semantics for payment + execution + trust feedback:

  • What must be locked before payment (intent: license/constraints/price/expiry)
  • What must be proven after a paid run (version, input/output hash, constraints, payment reference, signatures)
  • How consumers can submit verifiable ratings tied to actual execution

Execution repos (Solana/x402/Stripe/etc.) implement these contracts, but the contracts themselves stay portable here.

License

Copyright © 2026 Daud Zulfacar, Pandr UG (haftungsbeschränkt)

Apache License 2.0 — see LICENSE.

About

Chain-agnostic license semantics for the ProofMeta protocol

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors