Honey
Contribution layerHoney measures productive participation in the Hivemind ecosystem — earned by using, building, contributing, and growing.
- Earned, not bought
- Measures real participation
- The on-ramp to ownership
HivemindOS · Ecosystem plan
Honey is the contribution layer.
HIVE is the
ownership layer.
HivemindOS stays free and open source — the token supports the ecosystem, it never sits in front of the product. Paid services cover infrastructure HivemindOS operates for users: hosted rooms, managed compute, marketplace rails, and enterprise support.
Two layers, one ecosystem
Contribution and ownership, kept distinct on purpose.
Honey measures what you put in. HIVE represents what you own. The two are connected by a single action — claiming — and never confused for one another.
claim
HIVE
Ownership layerHIVE represents ownership of and alignment with the ecosystem. It sits above contribution — claimed with Honey, held or staked.
- Claimed with Honey
- Aligns the people building
- Locked while staked
Where claimable HIVE comes from
Honey claims are meant to be backed by real activity.
The reward pool is the bridge between contribution and ownership. Usage creates Honey; Honey can claim HIVE from a pool funded by ecosystem revenue, treasury allocation, and early seed funding while revenue is still growing.
Capped reward pool
Honey claims draw from an explicit ecosystem reward pool. The claimable HIVE is not meant to be unlimited inflation or rewards from thin air.
Revenue replenishment
Long term, managed compute, Hive Cloud, marketplace fees, enterprise services, and premium features fund the Honey reward pool.
Early seed funding
Before revenue is meaningful, the pool may be seeded with treasury allocation and a portion of existing HIVE trading-fee revenue so users can earn from day one.
The constraint: Honey is a contribution accounting layer, not an infinite faucet. If the ecosystem does not generate enough real value, the reward pool should stay capped instead of pretending yield exists.
Earning Honey
Four paths to productive participation.
Usage-based earning is the foundation and is live today. Creation, contribution, and growth are designed as future additions — each one rewarding a different way of strengthening the hive.
Usage
The current usage-based system remains the bedrock of Honey.
Foundation · live- Running agents
- Running swarms
- Using compute
- Using HivemindOS services
Creation
Reward the builders who extend what the hive can do.
Future addition- Publishing agents
- Publishing workflows
- Publishing swarms
- Creating marketplace content
Contribution
Reward the work that keeps the open-source core healthy.
Future addition- Open-source contributions
- Bug fixes
- Documentation
- Tutorials
- Community support
Growth
Reward the people who bring the ecosystem to more builders.
Future addition- Referrals
- Bringing new users
- Ecosystem promotion
Premium services
Revenue comes from optional services that cost real money to run.
The core stays free. Revenue is generated only by the managed, hosted, marketplace, and enterprise offerings layered on top — the fuel that powers operations, growth, treasury reserves, and revenue-backed buyback capacity.
Cloud Agent Calls
Managed LiveKit/SFU rooms for mobile-friendly, multi-party, and multi-agent voice calls.
Live paid path- Managed rooms
- Participant tokens
- Voice worker dispatch
- Hosted reliability
Hive Cloud
Managed HivemindOS hosting, fully operated for you.
Managed hosting- One-click deployment
- Managed infrastructure
- Hosted memory
- Team workspaces
- Monitoring
Managed Compute
Run agents and swarms on Hivemind infrastructure — pay only for usage.
Pay per use- Agent & swarm runtime
- Usage-based billing
- Elastic capacity
Agent Marketplace
Buy and sell across the hive. Hivemind takes a marketplace fee.
Marketplace fee- Agents
- Swarms
- Workflows
- Templates
Enterprise
Business customers pay for control, compliance, and support.
Contracts- SSO
- Teams
- Compliance
- Private deployments
- Support contracts
Payment rails
HIVE is a payment rail, not a toll booth.
Paid services should support multiple checkout paths. Crypto-native users can pay with HIVE where supported, while ordinary users can still use card, fiat, managed credits, x402 endpoints, or enterprise contracts.
Card / fiat
ordinary checkout for ordinary users
Managed HONEY
spend-only service credits for hosted usage
Crypto + HIVE
token payments where the user chooses them
x402
pay-per-use APIs, workflows, and agent services
Enterprise
contracts, SSO, private deployment, support
Launch discount policyPaying with HIVE can earn a 3-5% checkout discount. Staking discounts can stack with it, capped at 30% of eligible HivemindOS platform margin.
Hard margin ruleDiscounts apply to platform margin, never below direct compute, provider, payment-processing, or infrastructure cost.
Current paid example
Cloud Agent Calls are paid because HivemindOS runs the room.
The free call path stays BYOK: one user, one selected agent, the user's OpenAI Realtime key. Cloud Agent Calls add managed LiveKit rooms, SFU routing, participant tokens, voice-worker dispatch, multi-human calls, multi-agent calls, and hosted reliability.
CapabilityBYOK callsCloud calls
One user calls one selected agentIncludedIncluded
Uses user's OpenAI Realtime key directlyYesOptional
Managed LiveKit roomsNoYes
SFU audio routingNoYes
Multiple humans or agents in one callNoYes
Hosted room reliabilityNoYes
Marketplace economics
Creators choose the model that fits the agent, workflow, or skill.
The Agent Marketplace can support paid agents, swarms, workflows, templates, skills, plugins, monetization playbooks, and automation packages. HivemindOS can take a platform fee while HIVE staking improves trust, curation, visibility, and eligible fee discounts.
01Free
02Pay-per-use
03Lifetime access
04Subscription
05Bounty funded
06Commission on earnings
Bankr rail: Bankr supplies wallet, token, LLM gateway, and x402 primitives that map well to self-funding agent workflows, while HivemindOS keeps the local-first operator environment and marketplace surface.
Revenue allocation
Where every dollar goes.
Initial allocation. Company operations covers founder salary, development, hosting, infrastructure, contractors, legal, and accounting.
0%
0%
0%
0%
Treasury reserves
Value generated by the ecosystem builds reserves first.
The treasury exists to strengthen HivemindOS long-term. Buybacks are a separate, revenue-dependent policy lever — momentum when premium services work, not a promised demand floor.
Treasury firstRevenue builds reserves the ecosystem can use for durability, contributors, and growth.
Buybacks are conditionalOpen-market purchases happen only as revenue allows; they do not guarantee a price or floor.
Funds ecosystem growthTreasury funds flow back into Honey reward pools, grants, hackathons, and incentives.
As revenue comes in
Revenue
Buyback capacity
Acquire HIVE
The alignment it creates
More users
More revenue
More buyback capacity
Treasury funds may be used for
Honey reward poolsGrantsHackathonsEcosystem incentivesMarketingLiquidity supportPartnerships
Future burning
Burning is not a launch feature.
It may be considered later — but only once revenue is substantial, the treasury is healthy, and ecosystem funding is secure. The priority stays in order.
01Build productPriority
02Grow revenuePriority
03Build treasuryThen
04BuybacksThen
05Consider burnsLast · maybe
Staking
Staking should provide ecosystem benefits — not simply print more tokens.
Users stake HIVE when they want alignment benefits. They still own the HIVE, can exit after the visible cooldown, and the core product remains usable without holding or staking. The stake-lock is the real locked supply; buybacks remain separate and revenue-backed.
Holder
1m HIVEWallet-linked identity and basic status
0% managed-service discountSupporter
10m HIVECommunity access and stronger signal
5% managed-service discountBuilder
50m HIVEEarly workflows and contributor status
10% managed-service discountCurator
100m HIVEMarketplace power-user and bounty curation
15% managed-service discountOperator
250m HIVEEcosystem operations influence and higher trust
20% managed-service discountVisionary
1b HIVEHighest alignment, access, status, and limited council eligibility
25% managed-service discountSeat capFirst cohort capped at 12 active seats; expand only after the cadence is consistently honored.
CadenceMonthly council session plus async agenda; missed commitments are caught up before new seats are issued.
Good standingHard violations only: fraud, scams, harassment, doxxing, impersonation, or legal/safety violations. No open-ended discretion.
Holder identity and status
Alpha rooms and early drops
Marketplace trust signals
Bounty boosting and curation
Managed-service discounts
Governance signaling
Higher Honey earning multipliers
Visionary council seats
Staking utilityIdentity, status, alpha rooms, curation, bounty visibility, marketplace trust, Honey multipliers, and governance signaling.
Safety boundaryNo tier grants treasury control, user-fund control, binding votes, admin access, or unilateral payout authority.
Ecosystem loop
A self-reinforcing flywheel between adoption and token value.
Click any node to trace its place in the cycle. Each turn of the wheel feeds the next.
auto-advancing · click to pin
Source map
Full monetization docs and presentation.
A sustainable flywheel between product adoption and token value.
HivemindOS is a free and open-source operating system for AI agents. Users earn Honey by participating — through usage, creation, contribution, and growth. Honey claims HIVE, while revenue from optional premium services funds operations, growth, treasury reserves, and separate revenue-backed HIVE buybacks.