> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openkol.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Revenue Model

> Monetization plans without compromising scoring integrity.

OpenKol monetizes **access and workflow**, not outcomes.

The one rule: **scoring stays deterministic and independent**.
Paying users can get more usage and deeper tooling — but never “better scores.”

***

## 1) Freemium core

Designed for low-friction onboarding.

Includes:

* a daily lookup cap for guests and free users
* public analysis pages and shareable previews
* basic profile views and medal filtering

Goal: users hit the “aha” moment fast.

***

## 2) Pro subscriptions (individuals)

For power users who verify calls daily.

Planned features:

* higher or unlimited lookups
* deeper history per KOL/token
* advanced filters (medal thresholds, risk flags, liquidity bands)
* alerts and watchlists (e.g., “notify me when a tracked KOL posts a new call”)

***

## 3) Team plans (projects, agencies, DAOs)

For organizations running campaigns or vetting promoters.

Planned features:

* multi-seat workspaces
* campaign tracking + reporting
* exports (CSV / sheets) for internal reviews
* partner shortlists based on verified performance

***

## 4) API access (developers and data partners)

For dashboards, terminals, and analytics partners.

Planned features:

* API keys + usage tiers (quota-based)
* call-level data (scores, ROI context, risk flags)
* profile metrics and leaderboards
* bulk export for research partners

***

## 5) Sponsored placements (optional, strictly separated)

Sponsored exposure may be offered **only** under these constraints:

* clearly labeled as sponsored
* never changes scoring inputs, weights, or results
* never overrides ranking logic in “top” lists unless explicitly shown as ads

If it threatens trust, it’s not worth it.

***

## Optional: token alignment (if applicable)

If OpenKol introduces a token, this page should explicitly explain:

* what the token is used for (utility)
* how demand is created (sinks)
* what value accrual exists (if any)
* emissions, vesting, and unlock schedule

Ambiguous “token vibes” reduce trust — clarity increases it.

***

## Next

* [Business plan](/docs/business-plan)
* [Go-to-market](/docs/go-to-market)