Usage-based Regulatory Tariffs
Governed access to real-world data, enforced at runtime and priced by execution risk.
No subscriptions. No plans. No negotiated contracts.
Base Pricing Rule
Access to governed data is priced using normalized access units. Each unit represents one enforced execution with a corresponding evidence bundle.
Reference unit
Audio / Video → per governed hour (e.g. $10 per hour as a market reference)
Data modality examples
Audio / Video → per hour
Text → per 1,000 governed tokens
Images → per dataset execution
Structured data → per governed request
All modalities are normalized internally using the same governance and risk framework.
Runtime risk multipliers
Final pricing is determined at execution time based on policy-enforced risk factors.
Usage type (training vs production)
Regulatory classification
Data sensitivity
Jurisdiction
Replay, audit or simulation access
Pricing governance
Data holders define base pricing for their datasets
Xase enforces access, billing, and evidence generation
AI Labs accept pricing at execution or do not access the data
Xase governance fee
Xase automatically retains a governance fee on every executed access. This covers policy enforcement, cryptographic evidence bundles, audit-ready logs, and billing infrastructure.
The fee is applied invisibly and requires no manual reconciliation.
Included by default
Runtime policy enforcement
Immutable decision & access logs
Cryptographically signed evidence bundles
Audit-ready export (regulatory & legal)
Automatic usage-based billing
FAQ
How is usage measured?
Usage is measured in normalized access units generated at runtime by the policy engine. Each unit corresponds to an enforced execution and its evidence bundle.
When is billing triggered?
Billing is triggered on executed access. If policy blocks access, no usage is executed and no billing occurs.
Can pricing change retroactively?
No. Pricing is determined at execution time and recorded as part of the evidence trail for that access.
Is pricing negotiable?
No. Pricing is a system rule: data holders define base pricing, and Xase enforces multipliers at runtime based on policy and risk factors.
What happens if a policy requires approval?
Access does not execute until the approval condition is satisfied. Only executed access generates usage and evidence.
How is evidence generated?
Every executed access produces audit-grade logs and a cryptographically signed evidence bundle that can be verified offline.