$PLUID Token
— The coordination asset for a staked, verifiable read mesh.
$PLUID aligns the people who run the read mesh, the apps that depend on it, and the holders who want elevated access. It is a coordination and access asset — not a claim on writes, which belong to validators.
What It Does
| Function | Type | Description |
|---|---|---|
| Node staking | secures reads | Operators stake $PLUID to serve reads. Stake aligns honest, fresh answers with rewards and makes misbehavior costly. |
| Access limits | raises ceilings | Held $PLUID raises your API rate limits without a subscription — the Staked tier. |
| Routing weight | mesh priority | Stake-weighted operators earn priority in mesh routing for the reads they serve. |
| Governance | parameters | Holders steer network parameters — limits, reward curves, and the read method allow-list. |
Staking to Serve
Running a node means staking $PLUID against the freshness of your answers. Honest, well-anchored reads earn protocol rewards; provably stale or incorrect answers are slashable. See Run a Node for operator details.
Holding for Access
You do not need to run a node to benefit. Holding $PLUID moves you up the tier ladder — higher sustained rate and burst window — with no monthly plan. Authentication still uses your x-api-key; the held balance sets the ceiling.
Why a Token at All
- Reads are a public good that still costs real infrastructure to serve well.
- Staking gives operators skin in the game for freshness and uptime.
- A shared asset lets access, incentives, and governance settle without a gatekeeper.
Utility, not a promise
$PLUID is described here by its role in the network. Nothing on this page is financial advice or a guarantee of value. Token mechanics and parameters evolve through governance — see the Roadmap.