For Investors

HivemindOS is a proprietary local-first control plane for running AI agents. It ships with a narrow public compatibility SDK and an archived MIT Community Edition.

HivemindOS has one product relationship with two compounding revenue engines:

1. Agent operations: Hivemind Cloud subscriptions, managed execution, hosting, models, APIs, enterprise controls, and implementation.
2. Agent economy: disclosed fees when HivemindOS agents trade, pay, call paid APIs, or transact through supported rails.

Cloud revenue is the nearer-term recurring base; transaction revenue is the asymmetric upside if agent commerce becomes a large market.

What is free

Local agents, local memory, local workflows, your own model keys (BYOK), linked machines, and self-hosted runtimes all work without a subscription. The free product is how people find HivemindOS, and it stays useful on its own.

What is paid

Customers pay when HivemindOS runs a service for them: an always-on agent, hosted schedules and monitoring, shared approvals and budgets, public app hosting, managed model and API access, or private enterprise deployment.

Wherever agents run, official reputation, entitlement, settlement, and payout decisions remain server-controlled. Local settings and client claims cannot create credit, entitlements, or payouts.

Subscriptions pay for the control plane. Agent hours, model and API calls, hosted apps, and storage are metered separately, so one seat cannot run an unbounded fleet. The Pro, Team, and Enterprise prices are launch hypotheses still being validated with customers.

Current metered add-ons

MiroShark’s hosted price is the complete customer price, with no extra local fee. A run that does not start is not charged.

Near-term pilot

Before self-serve pricing is proven, HivemindOS sells a bounded Managed Agent Operations Pilot: six weeks, $5,000 upfront, one production workflow, up to three managed agents, and conversion to Cloud Team or a separately contracted managed plan. It is a customer-development offer, not a separate product line.

Transaction fees

Selected transaction fees are live today:

• The 0.20%, 0.10%, and 0.50% platform fees have a $0.01 minimum and $10 maximum.
• Bankr copy trading charges no fee on trade size. Since 2026-10-04 it charges a $1 monitoring minimum every 30 days and a share of each new realized profit on verified live copies. The share is 10% under $1,000 of copied volume in the last 30 days, 8% from $1,000, and 6% from $10,000. HIVE staking takes 1 to 3 points off, and the share never goes below 5%. Copies started before 2026-10-04 keep the terms they started on.
• Fees are shown before confirmation and collected only after the main action succeeds. Paper trades, rejected actions, research, and unpaid calls are free.
• Robinhood Chain Stock Tokens are bought and sold with USDG, the chain’s dollar stablecoin.
• Base Builder Codes are attribution infrastructure, not a contractual fee. Rewards count only when actually earned.
• Ordinary Bankr swaps, cross-chain actions, token launches, prediction markets, NFTs, and automations do not create a separate HivemindOS platform fee. Hosted Bankr copy trading is the exception: each copied Base swap is verified, and a share is collected only from new realized profit.

How large transaction revenue could get

Transaction revenue is eligible volume times the realized take rate, plus partner rewards actually earned. Copy-trading revenue depends on realized profit rather than volume, so it is not part of this table.

Illustrative gross platform-fee sensitivity—not a forecast:

Real revenue depends on rail mix, caps, minimums, failed actions, provider costs, fraud, and regulation. The table shows operating leverage; it does not assume HivemindOS reaches these volumes.

How revenue is counted

Operating revenue is subscriptions, hosted products, managed-execution gross profit, transaction fees, and implementation work. Provider spend, transaction volume, marketplace GMV, provider payouts, and token activity are reported separately. Buyer collections are not automatically company revenue.

Where revenue goes

HivemindOS allocates 15% to HIVE buybacks and a separate 15% to the company treasury. Both are computed on a server-owned per-service allocation basis published in the official commercial catalog: realized margin for most managed services, recognized platform revenue for others. The treasury does not fund buybacks, and the tokenomics policy assigns no fixed use to the remainder.

The live HIVE Buyback Ledger is the source of truth for completed purchases and burns. Since 2026-09-30, the HIVE each buyback purchase buys is burned: it is sent to the burn address in a separate transaction, published on the same ledger. Purchases made before that date were not burned. Buybacks and burns create no staking payout, ownership right, treasury claim, or price promise. Details: Revenue Allocations And Treasury Boundaries.

Honey and HIVE

• Honey is one cumulative, non-transferable, non-spendable record of verified contribution. It is not cash and does not automatically convert to HIVE.
• Hivemind Cloud credits are separate purchased, spend-only service credits.
• HIVE is an optional ecosystem token. It is not company ownership, a required payment method, or part of the pricing ladder.

Staking HIVE is optional membership across six bee tiers, from Honeybee to Queen Bee. Tiers give higher Honey earning multipliers, higher free-agent usage multipliers, and member pricing advertised as up to 61% off on participating services. Exact service prices remain server-owned.

Tokenomics policies may change, pause, or end for legal, regulatory, tax, accounting, security, liquidity, or operational reasons. Material changes are published ahead of time with an effective date, and completed on-chain receipts stay on the public record.

Pages in this section