Zetta

Financial Identity Infrastructure for Autonomous Agents.

AI agents are becoming economic actors. They operate wallets, settle payments, and generate revenue — all onchain. But raw wallet data tells you nothing about who the agent is, whether it can be trusted, or what it's actually doing.

Zetta solves this. We give every autonomous agent a verifiable financial identity — indexed in a public registry, scored for transparency, verified through a manifest standard, and interpreted by Luca.

What Zetta does

• Indexes — 125+ autonomous agents across 5 ecosystems in a public registry
• Verifies — agents declare wallets via manifest, Zetta validates ownership
• Scores — Transparency Score (0–100) based on wallets, status, activity, evidence
• Classifies — settlement patterns: treasury, revenue, operational spend, inference
• Interprets — Luca writes financial verdicts and monitors agent finances
• Distributes — SVG badges, public profiles, embeddable cards, API data

Who it's for

The architecture

Three layers. Each one depends on the one below it.

Zetta  =  infrastructure  (index, verify, classify, display)
Luca       =  intelligence    (interpret, score, verdict, monitor)
$LUCA      =  ecosystem asset (API tier, priority verification)

What We Built

The full infrastructure stack — live today.

The Manifest Loop

From zero identity to verified financial profile in four steps.

Wallet manifest format

Add this file to your repo at .agent/wallets.json:

{
  "agent": "MyAgent",
  "ecosystem": "AEON",
  "x": "@MyAgent",
  "website": "https://myagent.xyz",
  "wallets": [
    {
      "address": "0x...",
      "role": "treasury",
      "chain": "base",
      "notes": "Primary treasury wallet"
    }
  ]
}

Verification tiers

Candidate          →  Indexed, no proof of ownership
Needs Verification →  Flagged for review
Wallets Declared   →  Manifest submitted + validated ← start here
Claimed            →  Wallet address matches declared wallet
Verified           →  Luca-reviewed, fully verified
Luca Managed       →  Luca actively monitors finances

Core Product

The pages that make up the financial identity infrastructure.

API Reference

Financial identity data for agents, builders, and prediction markets.

Public — no auth required

{
  "agents_indexed": 125,
  "wallets_declared_or_above": 15,
  "claimed_or_above": 4,
  "verified_or_above": 2,
  "by_status": {
    "Candidate": 89, "Wallets Declared": 12,
    "Claimed": 3, "Verified": 1, "Luca Managed": 1
  },
  "by_ecosystem": {
    "AEON":  { "total": 8, "wallets_declared": 2, "verified": 1 },
    "BANKR": { "total": 34, "wallets_declared": 5, "verified": 0 }
  },
  "markets": {
    "100_manifests_before_august": false,
    "50_claimed_before_q4": false,
    "top_ecosystem_by_verified": { "ecosystem": "AEON", "count": 2 }
  },
  "updated_at": "2026-06-07T12:00:00Z"
}

GET /api/badge/aeon
→ image/svg+xml — "aeon | Wallets Declared" (blue)

Cache-Control: public, max-age=60, stale-while-revalidate=300

# In a README:
![Zetta](https://www.x402books.xyz/api/badge/aeon)

{
  "agents": [
    {
      "name": "Aeon",
      "symbol": "AEON",
      "ecosystem": "AEON",
      "verificationStatus": "Wallets Declared",
      "treasuryHealth": "Active",
      "wallets": [
        { "address": "0x...", "label": "likely treasury" }
      ]
    }
  ],
  "fromSupabase": true
}

Registry — no auth required

POST /api/registry/fetch-manifest
Content-Type: application/json

{ "repo_url": "https://github.com/your-org/your-repo" }

{
  "ok": true,
  "agent": "MyAgent",
  "wallets": [
    { "address": "0x...", "role": "treasury", "label": "likely treasury" }
  ],
  "message": "Manifest submitted. 1 wallet(s) queued for Luca verification."
}

POST /api/registry/claim
Content-Type: application/json

{
  "agent_slug": "my-agent",
  "wallet_address": "0x..."
}

{
  "ok": true,
  "matched": true,
  "message": "Wallet matched — claim submitted for review."
}

Financial Intelligence — API key required

GET /api/v1/agent-financial-state?wallet=0x...&range=30d
Authorization: Bearer xb_live_...

{
  "wallet": "0x...",
  "range": "30d",
  "financial_health": {
    "total_income_usd": 91.20,
    "total_spend_usd": 42.80,
    "net_flow_usd": 48.40,
    "budget_status": "safe",
    "transaction_count": 128
  },
  "token_portfolio": [...],
  "top_counterparties": [...],
  "recent_transactions": [...]
}

GET /api/v1/agent-report?agentName=Aeon&days=7
Authorization: Bearer xb_live_...

$LUCA

The token for Luca — not for Zetta API access.

$LUCA is Luca's intelligence token. It unlocks the full power of Luca as a financial intelligence agent — deeper analysis, premium reports, and priority verification. It is not required to use Zetta or the registry API.

Access tiers

Monetization

Infrastructure companies monetize through trust, access, and data.

Roadmap

Six phases from v1 to the financial operating system for autonomous agents.

Security

Zetta AI is read-only. It never touches your funds.

What Zetta AI does not do

• Request or store private keys
• Execute transactions from any wallet
• Take custody of funds
• Access wallet signing capabilities
• Store raw wallet secrets

What Zetta AI does

• Reads public onchain USDC transfer data via Base RPC
• Stores Privy user IDs, email addresses, and X handles in Supabase
• Associates wallet addresses with user sessions (opt-in)
• Generates AI summaries using Claude Haiku (Anthropic)

Authentication

User authentication is handled entirely by Privy. Zetta AI does not implement its own credential store. Sessions are issued as HMAC-signed cookies with no sensitive data embedded.

Data handling

All wallet activity analyzed by Zetta AI is sourced from public Base chain data. No private transaction data, off-chain balances, or non-public information is accessed at any point.

FAQ

Common questions about Zetta AI.