Agent builder path
Go from thesis to runnable proof.
A practical route for builders who want agent payments, work verification, settlement receipts, and programmable credit without pretending the stack is production-certified.
Run demos
Start with the visible x402, MCP, API-payment, and credit-note flows.
Read Accord
Review the protocol repo for agreements, receipts, rails, and conformance.
Track metrics
See prototype agent-economy status and future event-stream slots.
Study credit
Follow the bounded Note pattern for agent-issued task credit.
Live cockpit
One board for the agent economy stack.
Sage receipts, Accord conformance, MCP, the npm widget, and the ErgoScript playground now sit on the same operational map. Green means live testnet proof. Yellow means useful but not a protocol pass yet. Gray means engineering debt we are deliberately tracking.
Public posture remains testnet-first. No mainnet readiness claim until receipt conformance, signed artifacts, registry evidence, exact script identity, and external audit manifests are published.
Sage paid turn
Premium questions can be priced as Ergo testnet Notes, verified, answered, and redeemed on chain when the signer is online.
Receipt source
New paid turns can persist Agreement JSON, Verification Receipt JSON, Settlement Receipt JSON, and chain evidence under one receipt API.
Accord/402 bridge
The bridge is deployed. The remaining gate is one post-storage paid receipt, a signed conformance artifact, and registry evidence.
MCP endpoint
The Streamable HTTP MCP service is deployed on Fly, pushed to GitHub, and now resolves through the public mcp.ergoblockchain.org endpoint.
Sage widget
The public package starts with activity-feed embedding. The paid chat/quote/verify/receipt widget is the next bigger surface.
ErgoScript playground
The playground works in production, and the webpack async WASM config clears the previous build warning.
問題所在
為何現有支付軌道 無法服務智能體
沒有持久身分
智能體隨時啟動消失。Stripe 要求 KYC、帳單帳戶與靜態商家 ID——這些對於短暫存在的自主程序而言根本無法適用。
僅支援一次性付款
智能體需要信用機制：先發行,後兌付。Stripe 沒有可程式化的 IOU 層。每次微呼叫都需要往返支付處理者。
沒有可程式化的接受條件
你無法告訴 Stripe「僅當智能體完成任務 X 並持有憑證 Y 時才接受付款」。邏輯存在於支付層之外——天生脆弱。
毫秒級經濟模型失效
透過 Stripe 發起一筆 $0.001 的 API 呼叫,手續費本身就超過了呼叫價值。這套基礎設施根本不是為任何規模的機器間微支付而建。
The Unlock
Verifiable workflows are table stakes. Programmable credit is the unlock.
A verifiable workflow proves that work happened. Programmable credit lets agents coordinate future work before final settlement: sub-agent budgets, task-conditioned Notes, reserve-backed claims, expiry rules and policy-constrained spending.
Payments move value. Verification proves work. Credit creates economic agency.
Payments
Agents pay for API calls, compute, data and tools without forcing every decision back through a human checkout.
Verification
Receipts, task hashes and acceptance predicates define whether the agreed work actually happened.
Credit
Bounded, redeemable Notes let agents coordinate work now and settle later under explicit rules.
解決方案
為何 Ergo 是正確的 基礎層
技術堆疊
智能體經濟技術堆疊
結算層與 Babel Fees 今日已在 Ergo 主網上線。Reserve / Note / Tracker / Acceptance Predicate 原語可作為 ErgoScript 合約使用;標準參考實作 ChainCash 是開源原型,尚未經過稽核。聲譽與持久身分仍是開放研究問題——也是最值得開發者探索的方向。
PoW 最終性,eUTXO 原子性,手續費約 $0.01
鏈上資本支撐——持有 ERG 或代幣作為已發行票據的擔保品
可驗證的記帳——追蹤餘額、信用額度、兌付歷史
可程式化 IOU——發行、轉讓和兌付鏈下貨幣
接受邏輯——「當且僅當……時接受此票據」——完全鏈上執行
無中心化預言機的智能體聲譽機制——活躍研究方向
跨工作階段的智能體持久身分,同時避免去匿名化
可以建構什麼
三種可組合的流程。兩種已在測試網上線,一種即將推出。
LLM 購買推論服務
智能體 → 發行票據 → API 提供方接受謂詞 → 交付代幣
一次呼叫,一個證明,無需持久帳戶。提供方自行設定接受規則——最小任務雜湊、最大信用額度、截止時間。
智能體信用支付
儲備部署 → 發行票據 → 追蹤器監控使用情況 → 自動結算
信用額度鏈上強制執行。無對手方風險——儲備合約即是銀行。
社群貨幣
儲備持有 ERG → 社群發行本地票據 → 接受謂詞定義規則
本地市場、算力合作社或智能體網路——每個都擁有自己的貨幣和信任規則。
Sage, on chain, right now
Sage is the concierge agent of this site — the same primitives the page argues for, running in production. Every paid query settles publicly. Below is the seller wallet's recent activity, fetched live from the Ergo testnet explorer.
Ecosystem
Who's Building on Ergo
Projects and teams actively building agent economy infrastructure on Ergo.
Building on Ergo? Get listed