Use Cases

DRIP is designed for products where access, work, or service delivery happens over time. Instead of one upfront payment, a wallet can keep a stream active while value is being delivered.

Common patterns

AI agent access

Allow an agent session, workflow, or premium model route only while a user's stream remains active.

API and service access

Gate API usage, hosted services, or compute access with a wallet-native payment stream.

Wallet-native subscriptions

Replace card subscriptions with an onchain stream that can be paused or cancelled from the payer wallet.

Contributor payouts

Pay contributors continuously during an engagement while retaining control over unvested funds.

Grants and bounties

Fund milestone work with a stream that vests over the active work period instead of paying everything upfront.

Digital services

Meter access to communities, tools, datasets, or private services using active stream status.

Where DRIP fits best

The user or buyer should be able to stop future payment.
The receiver should be able to claim funds as they vest.
Access should depend on payment status.
Both sides benefit from transparent onchain state.

What DRIP is not

DRIP is not a trading product, not a Raydium or yield strategy, and not a promise of returns. Its core purpose is streaming escrow and payment-aware access.