Utility
$PASS earns its place by doing real work in the network — metering usage, securing throughput, and carrying governance weight. It is never required to use the core API.
Design principle
Utility should follow usage, not the other way around. Every $PASS sink maps to something the network actually consumes — verifications, API throughput, or coordination — so demand for the token tracks demand for the product rather than speculation alone.
Usage credits
Platforms can pay for attestations and API calls in $PASS. Credits are debited per metered action — the same actions counted against the plan quotas today. Paying in token is optional; card-based plans (Free, Pro, Enterprise) continue to work unchanged.
Staking for throughput
Platforms can stake $PASS to unlock higher rate limits and priority processing during peak load. Staking aligns heavy users with the long-term health of the network: the more a platform relies on Passify, the more it benefits from committing stake.
| Lever | Effect |
|---|---|
| Stake size | Raises the platform's throughput ceiling. |
| Stake duration | Longer commitments earn better terms. |
| Unstake | Subject to a cooldown to discourage churn. |
Governance weight
$PASS carries voting weight over decisions that shape the network — which schemas are added, what default rules ship, and how the treasury is allocated. See Governance for the process.
Future utility
Additional mechanisms may be introduced through governance — for example, fee discounts for stakers, attester incentives, or grants funded from the treasury. New utility is added deliberately and only when it serves the network; the bar is real usage, not novelty.
Last updated