HivemindOS manual
HivemindOS Commercial Sequence
HivemindOS grows one customer relationship in stages. Each stage opens only when the one before it shows real demand. The product stays useful without a subscription, credits, a marketplace, or a token.
local adoption
-> first managed service
-> recurring cloud subscription
-> managed usage expansion
-> agent transaction expansion
-> enterprise controls
-> marketplace liquidity
Stage one: free local adoption
People build and run local agents, workflows, models, memory, and apps on their own machines with their own provider keys. This free product is how customers arrive and why they trust HivemindOS. It is not weakened to push cloud sales.
Stage two: first paid activation
The first purchases are concrete and pay-as-you-go:
- publish an app at a stable URL
- keep one agent running after your own machines turn off
- use a managed model or API without opening another provider account
- run a hosted MiroShark simulation from the shared HivemindOS balance or direct x402 (local simulation stays free)
The hosted MiroShark simulation is $1.20 per accepted run. That is the complete customer price, and a run that does not start is not charged.
Stage three: Hivemind Cloud subscription
Cloud Pro and Cloud Team charge for the persistent operating layer: schedules, monitoring, shared history, approvals, spending controls, deployment history, shared agents and memory, and audit trails. Managed infrastructure stays metered, because its cost grows with agent activity, not with seats.
Stage four: Agent Economy Transaction Expansion
As agents get budgets and do more economic work, HivemindOS earns disclosed fees on supported trading, payment, and routing actions.
| Economic action | Current HivemindOS economics |
|---|---|
| DEX swap | 0.20% platform fee |
| Supported live stock or tokenized stock execution | 0.10% execution fee |
| Paid x402 or Veil private-payment execution | 0.50% platform fee |
| Bankr-managed Base copy trade | $1 monitoring minimum every 30 days, plus 5% to 10% of each new realized profit on verified live copies |
| Eligible Hyperliquid perp fill | 0.005% builder fee |
| Qualifying Base x402 transaction | Builder Code attribution; rewards are contingent rather than guaranteed |
This engine should grow only while execution stays competitive, fees stay visible, and settlement success stays high. Ordinary wallet transfers and revenue earned outside HivemindOS stay free. Other Bankr actions (swaps, cross-chain actions, token launches, prediction markets, NFTs, automations) carry no HivemindOS fee; only hosted copy trading does. It charges no fee on trade size: after each copied swap is verified, a share is taken only from new realized profit.
The full rail list, with Robinhood Chain and minimums, is on the investor overview.
Stage five: enterprise
Enterprise is the same control plane with stronger deployment, identity, policy, reliability, and support commitments. It is sold only for capabilities that exist: private deployment, SSO, audit export, regional controls, and SLAs are each labeled available, pilot, or planned.
Stage six: marketplaces
An agent, workflow, or compute marketplace launches only after there is recurring buyer demand and suppliers can expect real utilization. Fees scale with what HivemindOS provides:
| HivemindOS role | Fee policy |
|---|---|
| External revenue with no HivemindOS involvement | 0% |
| Billing or settlement only | Small disclosed processing/platform fee |
| HivemindOS sources the buyer | 5–10% target |
| HivemindOS sources, hosts, executes, supports, and protects the transaction | 10–20% target |
GMV, provider earnings, and buyer spend are reported separately from net platform revenue. The compute marketplace has its own evidence gates.
Commercial gates
Expansion is evidence-gated:
| Gate | Evidence required |
|---|---|
| Self-serve subscription launch | Repeated paid activation and retained managed usage |
| Transaction-engine expansion | Repeated agent economic activity, competitive execution, visible fees, low failure rates, and positive contribution margin |
| Team expansion | Multi-user demand for approvals, budgets, and shared history |
| Enterprise selling | A repeatable enterprise use case plus security and support readiness |
| Agent/workflow marketplace | Retained buyers seeking reusable supply |
| Compute marketplace expansion | Sufficient demand to create provider utilization |
| HIVE utility changes | Product-market fit, specialist legal review, server-authoritative benefit definitions, and exact prospective public terms |
Metrics that matter
- activated and product-qualified workspaces
- paid conversion by activation path
- 30-day and 90-day paid retention
- recurring revenue per paid workspace
- managed usage gross profit
- fee-bearing agent transaction volume by rail
- realized net take rate and transaction-fee revenue
- successful fee settlement and post-action collection rate
- Base Builder Code-attributed transaction count and rewards actually earned
- verified successful agent outcomes per paid workspace
- support and infrastructure cost per workspace
- contribution margin
- expansion versus contraction
Payment volume, deployed agents, token activity, and marketplace GMV are supporting metrics. They do not replace net revenue, take rate, contribution margin, or retained customers.