A data offer describes the proposed use, rights, conditions, and price of a Data Product. Consumers can evaluate those terms together with the offering's purpose and required inputs.
Data usage contracts
Connect an accepted data offer to explicit rights, conditions, and access grants.
Inspect the terms
Connect agreement to access
Accepted contract terms provide the basis for the relevant access grants. The grant defines authorized operations and their scope; the agreement records the parties' conditions and obligations.
Access permission and spending authority answer different questions. Having funds does not authorize reading a dataset, and permission to read it does not authorize charging another party.
Keep obligations visible
Record effective periods and lifecycle changes with the agreement. A contract can describe duties that require human or organizational action; a recorded obligation does not mean every duty is automatically enforced by software.
Purpose-bound access explains the broader authority boundary. Governed data products describes the offering, while Payments and budgets covers financial authorization.
Developer reference
Technical details
Offer, acceptance, grant
An offer is versioned graph data. Acceptance binds parties, effective interval, permissions and obligations to the evaluated terms. Later offer edits cannot mutate that acceptance retrospectively.
ODRL supplies rights-policy vocabulary; Data Product descriptions identify the supplied capability. Execution resolves the accepted contract into access grants for the requesting principal, resource, action and purpose.
Enforcement scope
Expiry and usage restrictions are machine-checkable where supported by grant evaluation. A contractual duty requiring external human action needs separate evidence. Data-contract evaluation does not install a general ODRL policy decision point for every Story. A wallet reservation is a funding decision, not a data-access grant.