Overview
ARPP 0.1 (Agent Rights & Provenance Protocol) is an open protocol that lets a publisher sign a rights manifest stating licence, retrieval, training, commercial use, attribution, and expiry. The manifest is bound to a SHA-256 digest of the bytes actually served, so a changed page invalidates the claim. It also lets an agent record a receipt referencing the exact manifest it read, with no personal data in it. The protocol rides on plain HTTPS and an RFC 8288 Link header, with no new scheme, port, or crawler to install.
ARPP 0.1 was initiated by Piruz Afruz MB, Lithuania, and published as PARP until September 2026; existing /parp paths keep working as migration aliases. The specification is released as v0.1.0 and publisher adapters as arpp-integrations v1.0.1 for Node, PHP, .NET, and Shopify starters. LLMBOO runs it in production, signing manifests with an Ed25519 publisher key, and provides a receipt intake endpoint.
ARPP is not DRM, not proof that an agent obeyed a policy, not legal advice or a licence agreement, not an IANA registration, and not authentication. Receipts are opt-in, public, and deleted after 90 days; the stored fields are id, manifest digest, agent URL, purpose, issue time, and arrival time.
Pricing
Free
Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.
Visit WebsitePrices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.
Use Cases
- Publishers use ARPP to sign a rights manifest covering licence, retrieval, training, commercial use, attribution, and expiry.
- Publishers use ARPP to bind a manifest to a SHA-256 digest of the served bytes so a changed page invalidates the claim.
- Agents use ARPP to record a receipt referencing the exact manifest they read, without personal data.
- Implementers use ARPP to serve manifests over plain HTTPS with an RFC 8288 Link header, without a new scheme, port, or crawler.
- Publishers use ARPP to accept voluntary receipts that are public and deleted after 90 days.
- Developers use ARPP integrations to publish ARPP out of the box via free WordPress and OpenCart plugins.
- Verifiers use ARPP to fetch a publisher key, fetch a manifest, and check the signature and digest against served bytes.
Features
Sign publisher rights manifests
Specify permitted content uses
Bind manifests to served content digests
Record receipts for consulted manifests
Verify manifest signatures and content digests
Serve manifests through standard HTTPS links
Reviews
No reviews yet. Be the first to share your experience!