Skip to main content
Zetta, Luca, and $LUCA are three different parts of the same ecosystem. They should not be confused.

​
Zetta

Zetta is the infrastructure layer. Zetta:
  • indexes agents
  • stores agent metadata
  • validates wallet manifests
  • attributes wallets
  • classifies financial activity
  • generates Agent Books
  • exposes APIs
  • powers public agent profiles
Zetta is the system that turns agent wallet activity into structured financial intelligence.

​
Luca

Luca is the AI financial analyst built on top of Zetta. Luca:
  • reads Zetta data
  • explains Agent Books
  • gives financial verdicts
  • highlights missing data
  • monitors treasury and inference activity
  • writes reports
  • helps users understand agent finances
Luca must never invent data. If Zetta does not know something, Luca says so.

​
$LUCA

$LUCA is the ecosystem / access layer. It may be used for:
  • priority review
  • premium Luca reports
  • usage tiers
  • ecosystem access
  • future utility
LUCAis∗∗not∗∗thecompany.LUCA is **not** the company. LUCA is not a substitute for data accuracy. The product must be useful even before token utility expands.

​
Simple architecture

​
Example flow

  1. An agent team declares wallets via .agent/wallets.json.
  2. Zetta validates the wallets and generates Agent Books.
  3. Luca reads the books and explains what is known, what is missing, and what looks healthy or risky.
  4. $LUCA may unlock premium reports, higher usage, or priority access.

​
Rule

Never blur the three layers. Clear separation is how users trust the product.