HivemindOS manual
HivemindOS Paid Capabilities
Paid capabilities are the parts HivemindOS operates for a customer. The local-first product remains free; the managed service charges for persistent availability, governance, collaboration, deployment, provider access, and support.
One Platform, Two Revenue Engines
HivemindOS has one customer relationship with two primary engines:
- Agent operations: workspace subscriptions plus metered infrastructure, hosting, models, APIs, and enterprise controls.
- Agent economy: disclosed trading, payment, routing, and later marketplace economics when governed agents transact.
Individual features below are capabilities, usage meters, and transaction rails inside that relationship—not separate businesses.
Available Managed Capabilities
Managed Cloud Agents
Dedicated always-on Hermes runtimes with persistent storage, managed inference, metering, and start/stop controls.
Open managed agentsApp Builder And Hosting
Share previews and renewable static, Pro, and dynamic apps published from local, linked, or managed projects.
Open hosting economicsManaged Models And APIs
Provider access, unified billing, receipts, routing, budgets, and server-side credential custody when users do not bring their own keys.
Open pricing modelCloud Agent Calls
Managed voice-room infrastructure for multi-device, multi-party, and multi-agent calls where available.
Open cloud callsAvailable Transaction Economics
| Rail | Current economics | Status |
|---|---|---|
| DEX swaps | 0.20% | Live |
| Supported live stock/tokenized-stock execution | 0.10% | Live |
| Paid x402 and Veil private-payment execution | 0.50% | Live |
| Bankr-managed Base copy trades | 0.50% ($0.02 minimum, $0.50 maximum) | Live after independent execution verification |
| Eligible Hyperliquid perp fills | 0.005% | Live builder fee |
| Base x402 Builder Code | Attribution and potential rewards | Live attribution; rewards not guaranteed |
These rails are documented in the Trading guide and Wallets, Honey, And x402. Ordinary Bankr swaps, cross-chain activity, token launches, prediction markets, NFTs, and automations remain product capabilities without a separate HivemindOS fee; the hosted Bankr copy-trading monitor is the explicit exception.
Validation And Later Expansion
| Capability | Status rule |
|---|---|
| Cloud Pro and Cloud Team | Design-partner validation until paid retention is observed |
| Enterprise controls | Sell only capabilities that are implemented and supportable |
| Agent/workflow marketplace | Defer until recurring buyer demand exists |
| Compute marketplace expansion | Defer supply growth until providers can receive realistic utilization |
| Stake-tier member usage pricing | Server-enforced consumption pricing on participating hive products; never a payout |
| HIVE buyback allocation | 15% of each service’s server-owned allocation basis (realized margin for most managed services, recognized platform revenue for others) funds a separate HIVE purchase rail; confirmed purchases remain publicly receipted and HIVE is not burned |
| Company treasury allocation | A separate exact 15% of the same server-owned allocation basis goes to company treasury; the treasury does not fund buybacks and creates no holder claim |
| Outside tokenomics allocation | The remainder has no fixed use assigned by the tokenomics policy |
Billing Principles
- Show ordinary dollar-denominated prices and usage.
- Keep Hivemind Cloud credits spend-only, nontransferable, and nonredeemable.
- Permit BYOK and self-hosting; subscriptions monetize management and governance rather than key lock-in.
- Quote variable provider and infrastructure costs before commitment where practical.
- Cap money-movement fees and charge nothing for ordinary wallet transfers.
- Separate deterministic fee revenue from Base Builder Code attribution, contingent rewards, provider fees, and gross transaction volume.
- Do not make HIVE a required payment method or gate core product access on staking; stake-tier member usage pricing sets usage prices on participating hive products, never access.
- Do not promise features marked design-partner, contact-led, or planned.