# ElizaOS Intel — 2026-03-30

## 1) Data Pattern Recognition (Velocity, Engagement, Adoption, Pain Correlation)

### Development velocity (repo-level)
- **Monthly baseline (Mar 1 → Apr 1, elizaos/eliza):** 45 PRs opened (**16 merged**), **9 new issues**, **7 closed issues**, **36 active contributors**.
- **Last observed day (2026-03-29):**
  - **1 plugin registry proposal**: `@axnetfun/plugin-axnet` submitted to `elizaos-plugins/registry`.
  - **1 dependency bump**: `cryptography 46.0.5 → 46.0.6` in `elizaos/eliza` (`/packages/python`).
  - **High-intensity design thread**: cross-repo discussion on **x402 payment governance** (Dreamline Policy Facilitator + operator pre-authorization layer).

**Trend:** Core runtime is stabilizing (dependency hygiene, CI fixes earlier in month) while the ecosystem accelerates around **agent commerce primitives** (x402 + marketplaces + governance).

### Community engagement patterns (Discord)
- **Repeated theme across 3 days (Mar 27–29): “Ecosystem clarity vs fragmentation.”**
  - Mar 27: confusion about **Hyperscape ↔ Eliza** relationship.
  - Mar 29: debate about **Milady** being separate vs integrated; investors missing context that Milady is built on Eliza.
- **Builder-to-marketplace pull is increasing**
  - Mar 28: **TaskBounty** announces agent-native bounties + autonomous payouts (USDC/ETH/SOL) + OpenAPI spec.
  - Mar 29: **Orbis** launches agent-native **pay-per-call APIs using HTTP 402 + USDC on Base**.

### Feature adoption & usage signals
- **Milady beta live**
  - Incentive campaign: screenshot contest (BNB/SOL rewards).
  - Accessibility improved: “cloud access” (no download).
  - Shared cost expectation: **~$7.20/month for 1 always-on agent; ~$21.60/month for 3**.
- **Agent commerce adoption pressure**
  - Orbis + TaskBounty + Dreamline threads indicate rising expectation that Eliza agents can **autonomously discover, purchase, and execute external work/services**.

### Pain point correlation across channels
| Pain Point | Where observed | What it correlates with |
|---|---|---|
| Ecosystem fragmentation / unclear project relationships | Discord discussion channel (Mar 29), governance Qs (Mar 27) | Investor confusion, weaker token narrative, duplicated community ops load |
| “Autonomous payments need governance & operator visibility” | GitHub cross-repo x402 thread (Mar 29) | Safety risk, trust barrier for enterprises, blocks wider adoption of paid APIs |
| Developer onboarding ambiguity (agent challenge endpoints / model costs) | Discord (Mar 29) | Drop-off risk for new builders; support burden |
| Security/scam attempts in community channels | Discord coders (Mar 29) | Reputation risk; need for hardened community safety ops |
| Infra reliability (job runner billing failure) | xfn-framework dev channel (Mar 29) | CI delays → slower merges/release cadence |

---

## 2) User Experience Intelligence (Themes, Impact, Sentiment, Opportunities)

### Feedback themes (categorized by impact)

**High impact (blocks adoption / trust)**
1. **Ecosystem understanding & navigation**
   - Users/investors can’t easily tell which apps/agents/tokens are “Eliza-native” (Milady, SHAW, Hyperscape confusion).
   - Strong request: **single website hub** listing agents/apps/dApps/community projects with explicit relationships.
2. **Autonomous payment governance UX**
   - Open question: does x402 tooling provide **operator-visible events before fetch executes** or only after wallet balance changes?
   - Without pre-authorization + audit trail, operator trust is low for “agents spending money.”

**Medium impact (growth / conversion)**
3. **Builder onboarding clarity**
   - Direct question unanswered: agent challenge endpoint provisioning and whether builders must pay OpenRouter/OpenAI.
   - Framework being open source is helpful, but cost expectations are unclear.
4. **Plugin submission & distribution**
   - Builders want predictable timelines and a known process for inclusion in main plugin repo/registry.

**Ongoing risk (community safety)**
5. **Scam prevention**
   - Multiple scam warnings; impersonation attempt flagged.
   - Community vigilance exists, but requires stronger preventative UX.

### Usage patterns vs intended design (observed mismatch)
- Intended: “ElizaOS as a unified framework/ecosystem.”
- Actual: users treat ElizaOS projects as **separate brands/servers**; knowledge is **tribal** and channel-specific (dev vs trader/investor).
- Intended: “x402 enables autonomous paid calls.”
- Actual: operator governance layer is not yet standardized, creating hesitation to deploy “spend-enabled agents.”

### Sentiment snapshot
- **Positive:** excitement around agent-native marketplaces (TaskBounty, Orbis) and real-world agent commerce.
- **Cautious:** concerns about payment safety/governance and brand fragmentation.
- **Alert:** scams/impersonation remain active.

### Implementation opportunities (near-term UX wins)
- Add **“Built on ElizaOS” relationship badges** for ecosystem projects (Milady, Hyperscape, SHAW-related items) across web + Discord.
- Publish a **single “Agent Challenge: Costs & Endpoints”** page to reduce repeated onboarding questions.
- Define a **standard operator approval UX pattern** for x402 (events, prompts, budgets, audit logs).

---

## 3) Strategic Prioritization (Impact vs Risk, Dependencies, Resourcing)

### Priority initiatives (next 2–4 weeks)

#### P0 — Ecosystem Hub + Relationship Clarity (High impact, Low–Med risk)
**Why now:** Repeated confusion is directly harming conversion (investors) and onboarding (builders).
- Deliverables:
  - Website “**Ecosystem Directory**” (agents/apps/dApps/community projects) with:
    - relationship type: *Eliza Labs / incubated / community-built / partner-integrated*
    - links: repo, docs, Discord entry point, token (if any) + “how it relates to ElizaOS”
  - “**Milady built on ElizaOS**” canonical explainer page and shareable link.
- Dependency: light PM + web/docs capacity; no core runtime changes required.
- Success metrics:
  - Reduce repeated Discord questions on “what is X to Eliza?” (track weekly count).
  - Increase click-through to “Start Building” from directory pages.

#### P0 — x402 Spend Governance Standard (Very high impact, Medium–High risk)
**Why now:** Orbis/TaskBounty-style marketplaces depend on trusted autonomous payments.
- Resolve the key unknown: **operator-visible event timing** in x402 plugin flow (pre-fetch vs post-balance-change).
- Recommend implementing a minimal standard:
  1. **Pre-flight event hook** (`onPaymentRequired` / `before402Settle`) emitting: vendor, amount, chain, purpose, correlation id
  2. **Policy decision interface**: allow/deny + budget gates + whitelist/blacklist
  3. **Audit log spec** (immutable-ish): request hash, decision, settlement tx, agent id
- Dependencies:
  - Core/runtime fetch wrapper or x402 plugin instrumentation
  - Agreement across `elizaos/eliza` and `elizaos-plugins/registry` maintainers
- Success metrics:
  - Time-to-integrate governed paid APIs (Orbis/Dreamline) measured by reference implementation completion
  - Reduction in “unsafe spend” concerns in community threads

#### P1 — Discord Bridging + Information Architecture (Medium–High impact, Medium risk)
**Goal:** Reduce fragmentation while preserving differing audiences (builders vs traders).
- Action: pilot **bridged room(s)** between Shaw dev Discord and main Discord for:
  - announcements
  - “built on ElizaOS” project updates
  - security alerts (scam/impersonation)
- Dependency: community ops coordination + moderation model alignment.
- Success metrics:
  - Reduced duplicate Q&A across servers
  - Increased awareness of Milady/Hyperscape relationships (poll/engagement)

#### P1 — Builder Onboarding: Agent Challenge + Model Cost Clarity (Medium impact, Low risk)
- Publish:
  - what endpoints are provided (if any)
  - recommended free/local model paths vs paid providers
  - expected monthly costs (use Milady cost examples as reference ranges)
- Success metrics:
  - Fewer unanswered onboarding questions
  - Increased agent challenge participation conversion

#### P2 — Infra Reliability: CI/Job Runner Billing Alerting (Medium impact, Medium risk)
- Fix root cause of “job not started due to failed account payments/spending limit.”
- Add:
  - billing status checks + alerting
  - documented ownership (who can raise limit, where)
- Success metrics:
  - Reduced CI downtime incidents/month
  - Improved PR merge throughput during releases

---

## Resource allocation recommendation (this week)
- **40%** Web/docs + ecosystem IA (Directory + relationship pages + agent challenge onboarding page)
- **40%** Core/payment governance (x402 pre-authorization hooks + reference policy facilitator integration)
- **20%** Community ops & safety (bridge pilot plan, scam prevention SOP, pinned security guidance)

---

## Key Risks to Monitor
1. **Governance lag blocks marketplaces:** Without a standard pre-authorization UX, Orbis/TaskBounty-like integrations may remain niche or unsafe.
2. **Brand fragmentation erodes narrative:** Multiple Discords/brands without a canonical map reduces investor confidence and builder trust.
3. **Scams impact reputation:** Repeated impersonation attempts require proactive countermeasures (verification UX + rapid comms).
4. **CI billing failures silently reduce velocity:** If job runners fail intermittently, merges and releases stall unpredictably.

---

## Actionable Next Steps (Owner-ready)
- **Define “Ecosystem Relationship Taxonomy”** (Eliza Labs / incubated / community / partner) and apply to Milady, Hyperscape, SHAW-related projects.
- **Ship v1 Ecosystem Directory** on website with search + tags + “Built on ElizaOS” badges.
- **Answer x402 operator visibility question** by instrumenting current x402 flow and documenting observed event points; decide hook location.
- **Draft x402 Governance Spec (MVP)**: event hook + policy response schema + audit log fields; align with Dreamline pre-auth proposal.
- **Publish Agent Challenge Onboarding FAQ** (endpoints + model/provider cost expectations).
- **Implement Discord bridge pilot** (announcements + security + ecosystem-updates) with moderation guidelines and escalation path.