For Investors

HivemindOS is a free and open-source control plane for autonomous agent operations.

HivemindOS has one product relationship with two compounding revenue engines:

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

Free local HivemindOS
  -> agents run through Hivemind Cloud
     -> subscription + managed usage + enterprise revenue
  -> agents transact through governed rails
     -> trading + payment + routing revenue

This is not eight unrelated businesses. It is one agent operating platform monetized when agents are operated and when they conduct economic activity. Cloud revenue is the nearer-term recurring base; transaction revenue is the asymmetric upside if agent commerce becomes a large market.

The Free-To-Paid Boundary

Local agents, local memory, local workflows, BYOK models, linked machines, and self-hosted runtimes remain available without a Hivemind Cloud subscription.

Customers pay when HivemindOS operates an ongoing service on their behalf:

• always-on agent runtime and persistent workspace
• hosted control plane, schedules, monitoring, and deployment history
• shared agents, approvals, budgets, and audit history
• public app hosting and isolated dynamic execution
• managed model and API access without customer-owned provider accounts
• private deployment, identity controls, support, and service commitments

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

Commercial Plans

The managed service owns the official catalog. Launch packaging is intentionally small:

Subscriptions pay for the control plane and governance layer. Agent hours, model/API calls, hosted apps, storage, and other variable infrastructure remain separately metered. This prevents a one-seat workspace from operating an unbounded fleet for one seat fee.

The Pro, Team, and Enterprise numbers are launch hypotheses under validation, not proven willingness-to-pay claims. They should change only through customer evidence and server-authoritative policy.

Current Metered Add-Ons

These products are expansion usage inside Hivemind Cloud. They are not separate investor pillars.

Current Agent Economy Revenue Rails

Selected transaction economics are already live in official HivemindOS policy:

The general 0.20%, 0.10%, and 0.50% platform-fee rails use a $0.01 minimum and $10 maximum where a fee applies. Bankr copy trading instead uses a $0.02 minimum and $0.50 maximum. Fees are disclosed before confirmation and settle only after the main action succeeds. Paper trades, rejected actions, read-only research, and unpaid calls do not create a fee.

Base Builder Codes are attribution infrastructure, not a contractual fee. They can make qualifying Base activity measurable and eligible for program rewards as those programs evolve, but rewards should be recognized 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 explicit exception because the managed monitor independently verifies each copied Base swap before collecting its bounded fee through Bankr.

Why Transaction Revenue Can Become The Largest Engine

Agent operations create recurring revenue per customer. Agent commerce can create revenue on every eligible economic action across every participating agent.

gross transaction revenue
= eligible agent transaction volume
x realized net take rate
+ builder or partner rewards actually earned

Illustrative gross platform-fee sensitivity—not a forecast:

Actual realized revenue depends on rail mix, caps, minimums, failed or reversed actions, rebates, provider economics, settlement cost, fraud loss, and regulatory constraints. The table demonstrates operating leverage; it does not assume that HivemindOS will reach those volumes.

Near-Term Customer Development

Before presenting self-serve pricing as validated, HivemindOS should sell a bounded Managed Agent Operations Pilot:

• six weeks
• $5,000 upfront
• one production operating workflow
• up to three managed agents
• monitoring, approvals, spending boundaries, deployment, and outcome receipts
• explicit implementation limits
• conversion to Cloud Team or a separately contracted high-touch managed plan

The pilot is a customer-development and implementation offer, not a permanent fifth product line.

Revenue Reporting

Operating revenue should be shown as:

subscription revenue
+ hosted product revenue
+ managed execution gross profit
+ transaction and routing fee revenue
+ implementation revenue

Provider spend, eligible transaction volume, gross payment volume, marketplace GMV, creator/provider payouts, and token activity are reported separately. Builder attribution is not revenue until a reward is actually earned. Buyer collections are not automatically company revenue. Principal-versus-agent accounting treatment requires review for each managed-provider and marketplace arrangement.

The operating model should be built from observed cohorts:

activated workspaces
x product-qualified conversion
x paid conversion
x retained subscription revenue
+ usage expansion

Investor reporting should include paid workspaces, 30/90-day retention, recurring revenue per workspace, usage gross profit, support cost, contribution margin, fee-bearing transaction volume, realized take rate, transaction-fee revenue, successful settlement rate, and expansion versus contraction. Illustrative customer counts or transaction volumes without funnel, churn, rail mix, and cost assumptions are not forecasts.

Scale-Dependent Network Upside

Trading, payment, and routing fees are already active on selected rails. Their strategic value grows with the number of governed agents, the economic actions each agent performs, and the share HivemindOS can monetize without degrading execution quality or trust.

Marketplaces, compute-provider take rates, workflow commissions, provider partnerships, embedded swap economics, and HIVE utility remain additional scale-dependent options. They are not required to prove near-term willingness to pay, but they can deepen the transaction engine after retained demand exists.

0x documents embedded integrator fees and, for suitable commercial plans, trade-surplus economics. HivemindOS currently uses its separate official post-success execution fee on applicable routes; embedded 0x economics remain an additional integration opportunity rather than current revenue.

• Revenue earned outside HivemindOS carries no platform fee.
• Marketplace fees apply only when HivemindOS supplies measurable distribution, hosting, execution, billing, or protection.
• Ordinary wallet transfers carry no HivemindOS platform fee.
• Financial and marketplace take rates remain capped, disclosed, and measured separately from provider fees and gross transaction volume.
• Base Builder Code rewards, partner rebates, and similar programs are reported as earned revenue rather than assumed take rate.

HIVE And Honey Boundary

HIVE is optional ecosystem infrastructure. It is not company ownership, a required payment method, or part of the core pricing ladder.

Honey is one cumulative, non-transferable, non-spendable record of verified ecosystem contribution and bounded recognition, with source labels kept only for provenance. Hivemind Cloud credits are separate purchased, spend-only service credits. Honey is not cash and does not automatically convert to HIVE.

Staking HIVE is optional membership across six bee tiers: Honeybee, Bumblebee, Mason Bee, Orchid Bee, Carpenter Bee, and Queen Bee. The tiers preserve three benefits: 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.

HivemindOS allocates 15% to HIVE buybacks and a separate 15% to the company treasury, each 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 the buybacks, the two allocations use separate accounting rails, and the tokenomics policy assigns no fixed use to the remainder.

The live HIVE Buyback Ledger is the source of truth for execution status and completed purchases. It preserves Hive Research’s first paid production run and confirmed HIVE purchase on Base as historical evidence. HivemindOS does not burn HIVE. Buybacks create no staking payout, ownership right, treasury claim, price promise, or Honey-to-HIVE conversion.

Tokenomics policies may change, pause, or end in response to legal, regulatory, tax, accounting, security, liquidity, market-integrity, reserve, or operational requirements. Material changes are published prospectively with an effective date, while completed on-chain receipts remain part of the historical record.

See HIVE Token Receipts, Honey, HIVE, And Treasury, Revenue Allocations And Treasury Boundaries, and HIVE Staking And Community Tiers for the on-chain evidence and separated policies.

One-Sentence Pitch

HivemindOS is the open-source control plane for the agent economy: teams pay it to operate governed agents, and HivemindOS earns again when those agents transact through supported trading, payment, and routing rails.

Read Next

• Ecosystem Plan
• Paid Features
• App Builder And Hosting
• Hive Compute Marketplace