# ElizaOS Weekly Newsletter (2026-03-30) **Week of 2026-03-23 → 2026-03-29** ## 1) Executive Summary **1) “Agent Commerce” accelerated: pay-per-call APIs and spend governance took center stage.** This week’s conversations and repo activity converged on a clear theme: letting agents *safely* buy services. The community showcased new x402-compatible marketplaces (notably **Orbis**) and pushed forward governance patterns like the **Dreamline x402 Policy Facilitator** (pre-authorization and operator controls before funds move). **2) Ecosystem clarity became a top community priority.** Multiple members raised the same pain point: project/channel fragmentation makes it hard—especially for newcomers and token holders—to understand which agents and apps are part of the ElizaOS umbrella. A concrete proposal emerged to build a **centralized website hub** listing all agents, apps, dApps, and community projects, plus Discord **bridge rooms** to connect builder-focused and investor-focused spaces. **3) Core reliability and maintenance continued steadily.** On the engineering side, the week included routine security/maintenance improvements like a **Python `cryptography` bump (46.0.5 → 46.0.6)**, plus ongoing attention to CI/release health (including a reported billing/spend-limit issue affecting a job runner). --- ## 2) Development Updates (Core + Plugins) ### x402 payment governance: “operator-visible” controls before funds move A cross-repo design discussion gained momentum around the **Dreamline x402 Policy Facilitator** proposal—focused on how humans (or organizational policies) can approve/deny autonomous agent spending *before* execution. A key open question surfaced: **does the current x402 flow emit any operator-visible event before a `fetch` executes, or is the first signal simply a wallet balance change?** That answer will strongly shape any pre-authorization layer. - Relevant proposal (open): **Dreamline x402 Policy Facilitator** — `elizaos/eliza` Issue **#6695** https://github.com/elizaos/eliza/issues/6695 ### Plugin ecosystem growth: registry additions and submission process A new plugin proposal was submitted to the plugin registry: **`@axnetfun/plugin-axnet`**. At the same time, Discord discussions highlighted a recurring developer need: a clearer, documented path for **getting third-party plugins reviewed, accepted, and distributed**. - Registry PR (open): **Add `@axnetfun/plugin-axnet`** — `elizaos-plugins/registry` PR **#324** https://github.com/elizaos-plugins/registry/pull/324 ### Dependency maintenance: Python cryptography update A small but important security/maintenance update landed in core: **`cryptography` 46.0.5 → 46.0.6** under `packages/python`. ### Infra note: CI/job runner payment failure In the developer channels, a CI/job runner reported a failure due to **account payments/spending limits**, flagged for follow-up (and possibly connected to the “Soulmate Lang” org). If you’re seeing intermittent CI start failures, this may be related. --- ## 3) Community Spotlight (Discord Highlights) ### “Where does Milady live?”: ecosystem navigation and Discord bridging A lively discussion in **#discussion** tackled whether projects like **Milady** should have dedicated spaces *inside* the main ElizaOS Discord or remain separated. The core concern wasn’t just community preference—it was *discoverability*: several members noted that many people **don’t realize Milady is built on ElizaOS**, which creates confusion for investors and new builders. Two practical outcomes emerged: - A proposal to create a **bridged room** connecting different Discord spaces while keeping their distinct cultures (builder-focused vs trader/investor-focused). - A push for a **single, authoritative website hub** that explains relationships between projects (including clarity around SHAW and other ecosystem-adjacent launches). Milady status notes shared this week: - **Milady is live in beta** - A contest offering **BNB or SOL rewards** for screenshots - **Cloud access** announced (no download required) - Example operating cost estimates were shared (e.g., ~**$7.20/month** for one always-on agent; ~**$21.60/month** for three) ### Orbis: pay-per-call APIs for agents (HTTP 402 + USDC on Base) In **#coders**, **TheRedWizardDev** introduced **Orbis**, an API marketplace designed specifically for autonomous agents: - Implements **HTTP 402 Payment Required** - Agents can call an endpoint → receive a **402** → automatically pay in **USDC on Base** → receive the response - No subscriptions, no API keys, no human-in-the-loop required - Live endpoints include **text analysis**, **QR/encoding**, **form submission**, and **fake data generation** - A machine-parseable discovery endpoint is available (great for agent tool discovery) This is a strong real-world example of “Agent Commerce” infrastructure that’s composable with Eliza agents today. ### TaskBounty: autonomous task completion + agent-to-agent delegation economy Another major community share: **TaskBounty** announced integration patterns for Eliza agents to autonomously: - Browse tasks - Submit work - Receive crypto payouts (**USDC, ETH, SOL**) directly to agent wallets via REST API Notably, TaskBounty also supports **bidirectional task management**: agents can *delegate subtasks* to other specialized agents—an early blueprint for an agent-to-agent labor market. ### Security vigilance: scam warnings handled quickly Multiple users flagged scam activity (including impersonation), and the community responded quickly with warnings—good operational hygiene as the ecosystem grows. --- ## 4) Token Economics (AI16z + auto.fun) **AI16z → ElizaOS migration remains an active topic.** A user asked for help migrating from **AI16Z to ElizaOS**, reflecting continued movement of builders and users into the ElizaOS stack. While no step-by-step resolution was captured in the weekly logs, it’s a clear signal that **migration guidance** and “how it maps to token value” messaging are still needed. **Visibility and information architecture are now “token-holder critical infrastructure.”** This week’s strongest token-adjacent takeaway: holders and newcomers need a coherent story of *what is built on ElizaOS*, where to find it, and how projects relate. The community explicitly tied ecosystem clarity to the ability to evaluate the value of holding ecosystem tokens. **auto.fun:** no formal product updates were posted in the captured logs this week, but auto.fun remains present in community identity (roles, discussion context). If you’re building agent monetization flows, keep an eye on upcoming marketplace + payment-rail standardization (x402 patterns) that will likely feed into auto.fun-style distribution. --- ## 5) Coming Soon (What to Watch Next) - **Discord bridge room(s)** to reduce fragmentation while preserving specialized spaces (builders vs traders/investors). - **Centralized ecosystem hub** on the website: agents, apps, dApps, community projects, and clear relationship mapping. - **x402 pre-authorization standardization**: expect continued design iteration around operator prompts/events, policy contracts, and audit trails (Dreamline discussion is the current focal point). - **More agent marketplaces & endpoints**: Orbis invited feedback and plans to expand endpoints based on developer needs; TaskBounty integrations may inspire new “agent workforce” patterns. - **Clearer onboarding around model endpoints and the agent challenge**: builders asked whether they’ll need paid providers (OpenRouter/OpenAI) or whether endpoints are provided—this is ripe for documentation. --- ## 6) Resources (Links & Threads) ### Key discussions (Discord) - Ecosystem visibility + Milady channel strategy (thread context): https://discord.com/channels/1253563208833433701/1253563209462448241 ### Orbis (API marketplace for agents) - Discovery endpoint (machine-parseable catalog): https://orbisapi.com/api/agents/discovery ### TaskBounty (agent integration) - OpenAPI 3.1 spec: https://task-bounty.com/api/v1/openapi.json - Developer docs for agents: https://task-bounty.com/for-agents ### GitHub: payment governance + integrations - Dreamline x402 Policy Facilitator (open): https://github.com/elizaos/eliza/issues/6695 - Pyrimid x402 Agent Commerce via MCP (open): https://github.com/elizaos/eliza/issues/6668 - AgentID proposal (open): https://github.com/elizaos/eliza/issues/6688 ### GitHub: plugin registry - `@axnetfun/plugin-axnet` registry PR (open): https://github.com/elizaos-plugins/registry/pull/324 --- If you’re building this week: consider prototyping a small agent that (1) discovers paid endpoints via Orbis, (2) uses x402 to pay-per-call, and (3) logs or requests human pre-approval for spends—those three pieces are quickly becoming the ecosystem’s “default stack” for safe autonomy.