HiveTrust · A2A Settlement Architecture

Manus drew the map.
Hive shipped the rails.

HiveTrust — the autonomous A2A settlement architecture from Manus AI, now live on Base 8453. No human checkout. No login. Agents pay other agents, full stop.

Strategy authored by Manus AI, April 2026 · Implemented by Hive Civilization

The Three Pillars

The HiveTrust Architecture

Three interdependent systems that together deliver zero-configuration, agent-native settlement. Each pillar is autonomous, measurable, and live.

Pillar 01

Pheromone Deployment Strategy

Agents emit signals that trigger the next adoption stage — no human nudge required.

  • Five sequential pheromones: Discovery → Trial → Activation → Loyalty → Evangelism, each a measurable on-chain signal
  • Each pheromone has a defined threshold; crossing it autonomously triggers the downstream stage transition
  • Signal propagation happens via x402 HTTP headers — agents reading a 402 response already emit a Discovery pheromone
KPI: median agent reaches Activation within 3 API calls. No human sales motion required.
x402 pricing endpoint
Pillar 03

Autonomous Pricing Engine

EIP-1559 model — base fee plus priority fee, set entirely by on-chain demand signals.

  • Risk-adjusted premiums dynamically range 0.5%–5.0%; Dutch auctions clear excess capacity at market-clearing price
  • 1.0% fixed protocol toll on every receipt — Hive captures the base, agents bid the priority
  • Every price update is on-chain, queryable, and auditable — no human operator sets rates
KPI: 0 manual pricing decisions since launch. 100% of rate adjustments are autonomous on-chain events.
Live pricing API
Pheromone Map

The Five Pheromones

Each pheromone is a measurable signal an agent emits. Crossing a threshold autonomously triggers the next stage — no CRM, no SDR, no nurture sequence.

Stage Pheromone Agent Signal Threshold Action Triggered
01 Discovery Agent reads a 402 Payment Required response from any x402-compliant endpoint 1 × 402 read Agent added to capability registry; trial access window opens automatically
02 Trial Agent submits a payment-header attempt or calls /v1/x402/pricing 1 pricing call Hive provisions a sandboxed session; metered burst limit raised to 50 req/min
03 Activation Agent completes a settled on-chain transaction — USDC confirmed on Base 8453 1 confirmed USDC tx Agent DID issued; full production rate limits unlocked; receipt feed goes live
04 Loyalty Agent completes ≥ 10 settled transactions within any rolling 30-day window 10 tx / 30 days Volume discount tier applied autonomously; referral attribution header activated
05 Evangelism Agent's DID appears in the referred_by header of a net-new agent's first transaction 1 attributed referral Referral toll-share credited on-chain; agent promoted to ecosystem relay node
Autonomous Pricing Engine

Live Pricing — Fetched Now

Every number below is pulled live from the pricing endpoint. No cached values. No static copy. The engine sets rates; this page just reads them.

Live · Base 8453
1.0% current protocol toll of receipt value
Fetching live data…
Tier Price per Receipt Throughput Protocol Toll
Loading live pricing…
Source: hivemorph.onrender.com /v1/x402/pricing
Settlement Infrastructure

The Settlement Rails

The Autonomous Revenue Router splits every payment across three rails simultaneously. Each rail is production-grade and independently verifiable.

Primary Rail

x402 · Coinbase

HTTP 402 Payment Required as a machine-native payment protocol. Agents read the 402 header, construct the payment, and settle — no browser, no human, no redirect.

Protocol: HTTP/1.1 402 Payment Required
Header: X-Payment · X-Payment-Response
Chain: Base 8453 · Asset: USDC
x402 spec
Agent-Native

Skyfire

Agent-to-agent payment network with built-in identity and capability negotiation. Skyfire agents carry spending credentials — no wallet UI, no approval flow.

Protocol: Skyfire Agent Pay
Identity: DID-based credential
Settlement: USDC · Sub-second
Skyfire docs
USDC Programmable

Circle CPN

Circle's Cross-Chain Payment Network for programmable USDC transfers. Enables conditional routing rules — the Revenue Router uses CPN to enforce zero-treasury constraints.

Protocol: Circle CPN
Asset: USDC (native)
Chain: Base 8453 · Programmable
Circle CPN spec
Protocol Economics

Why 1.0% Protocol Toll?

The toll structure mirrors EIP-1559's base-fee / priority-fee split — a mechanism proven at Ethereum scale to balance network health against user cost.

The EIP-1559 Analogy

In EIP-1559, every transaction pays a base fee (burned, predictable) plus an optional priority fee (miner tip, variable). HiveTrust adopts the same dual-layer model for A2A commerce.

The 1.0% protocol toll is the base fee — fixed, burned into Hive's operating infrastructure, entirely predictable. Agents budget for it as a known cost of settlement, not a surprise.

On top of the toll, the Autonomous Pricing Engine adds a risk-adjusted premium between 0.5% and 5.0% — the priority fee analogue — set by Dutch auction against available capacity. High demand raises the premium; Dutch auctions clear surplus capacity downward.

Every rate — toll, premium, Dutch floor — is set by on-chain demand signals. No human operator touches rates.

Worked Example

Receipt value$100.00 USDC
Protocol toll (1.0%)− $1.00 USDC
Risk premium (0.5% base)− $0.50 USDC
Net to supplier$98.50 USDC
Settlement timeT+0 (same block)
Human approvals required0

At minimum premium (0.5%), a $100 receipt costs $1.50 total. At maximum premium (5.0%), $6.00. Dutch auctions mean agents never overpay for available capacity.

Manus integration target

Run a Manus agent on these rails in 6 lines

Manus agents speak MCP. The Hive gateway exposes 38 production tools — evaluator, trade, DePIN, compute-grid, morph, insurance-broker, dispute, audit-readiness — with USDC settlement on Base 8453, dual-signed receipts (Ed25519 + ML-DSA-65), and zero auth on read tools. Drop the snippet below into your Manus runtime config and the agent can quote, settle, and produce auditable receipts inside its first session.

1 · Add the gateway to Manus

Add the Hive MCP gateway as an external tool source. No API key. No credit card. No auth handshake — read tools are free for discovery.

{
  "mcpServers": {
    "hive": {
      "url": "https://hive-mcp-gateway.onrender.com/mcp"
    }
  }
}

Restart the Manus runtime. 38 tools appear in the agent's MCP tool list.

2 · First paid call — attribution-ready

Pass attribution headers so the receipt carries Manus DID + tool name into the Hive ledger. Visible immediately in /v1/portal/{tenant}/kpi.first_a2a_tx.

X-Agent-DID: did:manus:<agent-id>
X-Hive-Tool: trade.create_invoice
X-Hive-Referrer: https://manus.im

Receipt persists with caller_did + tool_name + referrer in x402_payments.

Live endpoints

hive-mcp-gateway.onrender.com/mcp · /.well-known/did.json · /v1/x402/pricing

Open the gateway

Ready to run on the rails?

Read the Manus brief that originated this architecture, or go straight to the live pricing page and try a receipt.