Homie Dev Docs

Architecture

Homie stacks onchain primitives on Base, offchain data and orchestration, and a property-aware assistant that routes work to internal flows and marketplace agents over A2A.

Layered system

Figure E in the protocol overview (whitepaper): contracts, backend services, AI orchestration + agents, and the web app—with a normal-app UX by default.

Frontend (Web2-style UI)
↓
AI orchestration (Genkit flows, tools; internal Surveyor / Appraiser / Auditor / Treasurer patterns)
↓
Marketplace registry + activity logging (e.g. marketplace_agents resolved when invoking an agent by agentId)
↓
Backend services & data layer
↕
Onchain layer (Base): identity, HOME, USDh, HOAM, treasury, AMM where enabled

Four-token model (summary)

The protocol separates identity, ownership, settlement, and governance. Classifications below follow the same table as the whitepaper (informational—not a regulator determination). Details: Smart Contracts.

AssetRoleClassification (per whitepaper)
Address TokenProperty identity (HomieANS)Digital Tool
HOMEFractional ownership shares (ERC-1155)Digital Commodity
USDhome / USDhStable settlement for fees and marketplaceGENIUS Act stablecoin (per whitepaper)
HOAMGovernance and protocol fee routingFunctional governance

Homie AI: flows, tools, agents

  • Genkit flows orchestrate multi-step workflows.
  • Tools gate side effects (database, web, A2A calls).
  • Internal agents cover onboarding (Surveyor, Appraiser, Auditor, Treasurer).
  • Marketplace agents extend the product via A2A calls you implement—see A2A Protocol.

Marketplace & discovery

Agents advertise capabilities via agent cards; Homie discovers and invokes them with JSON-RPC 2.0. Payments: credits for UX, settlement in USDh, with X402-style flows for fine-grained pricing (see Payments). Regulated services are supplied by third-party licensed providers through the marketplace.