HiveTrust · A2A Settlement Architecture

Manus drew the map.
Hive shipped the rails.

HiveTrust is the automatic A2A settlement setup from Manus AI, now live on Base 8453. No human checkout. No login. Agents just pay other agents.

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

The Three Pillars

How HiveTrust Is Built

Three systems work together here to give you settlement that just works for agents, no setup needed. Each pillar runs on its own, and each one is measurable and live.

Pillar 01

Pheromone Deployment Strategy

Agents send signals that trigger the next stage of adoption on their own, with no human nudge needed.

  • Five signals happen in order: Discovery, Trial, Activation, Loyalty, Evangelism. Each one is a signal you can measure on-chain.
  • Each signal has a set threshold. Crossing it automatically moves the agent to the next stage.
  • The signal travels through x402 HTTP headers. An agent reading a 402 response has already sent the Discovery signal.
KPI: median agent reaches Activation within 3 API calls. No human sales motion required.
x402 pricing endpoint
Pillar 03

Autonomous Pricing Engine

This uses the EIP-1559 model: a base fee plus a priority fee, both set entirely by on-chain demand.

  • Risk-adjusted premiums move between 0.5% and 5.0%. Dutch auctions clear extra capacity at the market price.
  • A fixed 1.0% protocol toll applies to every receipt. Hive takes the base, and agents bid on the priority.
  • Every price update happens on-chain, so you can look it up and check it. No human sets the rates.
KPI: 0 manual pricing decisions since launch. 100% of rate adjustments are autonomous on-chain events.
Live pricing API
Pheromone Map

The Five Signals

Each signal is something an agent does that we can measure. Crossing a threshold moves it to the next stage automatically, with no CRM, no sales team, no drip campaign.

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 gets added to the capability registry, and a trial access window opens automatically
02 Trial Agent submits a payment-header attempt or calls /v1/x402/pricing 1 pricing call Hive sets up a sandboxed session, and the burst limit rises to 50 requests per minute
03 Activation Agent completes a settled on-chain transaction, confirmed in USDC on Base 8453 1 confirmed USDC tx The agent gets a DID, full production rate limits unlock, and the receipt feed goes live
04 Loyalty Agent completes ≥ 10 settled transactions within any rolling 30-day window 10 tx / 30 days A volume discount applies automatically, and the referral attribution header turns on
05 Evangelism Agent's DID appears in the referred_by header of a net-new agent's first transaction 1 attributed referral The referral toll share gets credited on-chain, and the agent becomes an ecosystem relay node
Autonomous Pricing Engine

Live Pricing, Fetched Right Now

Every number below comes live from the pricing endpoint. Nothing is cached, nothing is static copy. The engine sets the rates, and 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: receipts.thehiveryiq.com /v1/x402/pricing
Settlement Infrastructure

The Settlement Rails

The automatic revenue router splits every payment across three rails at once. Each rail is production-grade, and you can check each one independently.

Primary Rail

x402 · Coinbase

HTTP 402 Payment Required works here as a payment protocol built for machines. Agents read the 402 header, put together the payment, and settle it. 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

This is an agent-to-agent payment network with identity and capability checks built in. Skyfire agents carry their own spending credentials, so there is no wallet screen and no approval flow.

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

Circle CPN

This is Circle's Cross-Chain Payment Network for programmable USDC transfers. It supports conditional routing rules, and the revenue router uses CPN to keep zero-treasury rules in place.

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

Why a 1.0% Protocol Toll?

The toll works like EIP-1559's base fee and priority fee split, a setup that Ethereum has proven at scale to balance network health against user cost.

How EIP-1559 Compares

In EIP-1559, every transaction pays a base fee that gets burned and stays predictable, plus an optional priority fee that works like a tip and moves around. HiveTrust uses the same two-part model for A2A commerce.

The 1.0% protocol toll is the base fee. It's fixed, it goes straight into running Hive's infrastructure, and it's fully predictable. Agents can budget for it as a known cost, not a surprise.

On top of the toll, the automatic pricing engine adds a risk-adjusted premium between 0.5% and 5.0%. That's the priority fee part, set by a Dutch auction against how much capacity is available. High demand pushes the premium up, and the Dutch auction brings surplus capacity back down.

Every rate here, the toll, the premium, and the Dutch floor, gets set by on-chain demand. No human touches the 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 the lowest premium (0.5%), a $100 receipt costs $1.50 total. At the highest premium (5.0%), it costs $6.00. Dutch auctions mean agents never pay more than they need to for available capacity.

Manus integration target

Run a Manus agent on these rails in 6 lines

Manus agents speak MCP. The Hive gateway gives you 38 production tools, covering evaluator, trade, DePIN, compute-grid, morph, insurance-broker, dispute, and audit-readiness, with USDC settlement on Base 8453, receipts signed twice (Ed25519 plus ML-DSA-65), and no login needed on read tools. Drop the snippet below into your Manus runtime config, and the agent can quote, settle, and produce checkable receipts in 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 login needed. Read tools are free to explore.

{
  "mcpServers": {
    "hive": {
      "url": "https://receipts.thehiveryiq.com/mcp"
    }
  }
}

Restart the Manus runtime, and 38 tools show up in the agent's MCP tool list.

2 · Your first paid call, ready to track

Pass attribution headers so the receipt carries the Manus DID and tool name into the Hive ledger. You'll see it right away 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

The receipt stays saved with caller_did, tool_name, and referrer in x402_payments.

Live endpoints

receipts.thehiveryiq.com/mcp · /.well-known/did.json · /v1/x402/pricing

Open the gateway

Ready to run on the rails?

Read the Manus brief behind this setup, or go straight to the live pricing page and try a receipt.