by 运行时依赖
安装命令
点击复制技能文档
API3 Feed 管理器 (Executor)
This 技能 is the oracle-enablement layer for 代理-built projects that need reliable, decentralized, onchAIn data feeds.
This is the executor-capable variant: it can prepare and, when explicitly 请求ed, submit funding transactions.
It is de签名ed to let 代理s:
find the correct API3 feed distin图形界面sh between feeds that are merely discoverable and feeds that are currently active determine whether a feed is already usable fund/activate it when possible mAIntAIn 运行way for continued operation
without requiring manual coordination with the API3 team.
When to use
Use this 技能 when:
a project needs a reliable, onchAIn, decentralized price feed an 代理 wants to 部署 something that depends on a live oracle an existing feed may need a top-up or 运行way 检查 a down流 技能 or 应用 needs feed activation as a prerequisite Core modes
- discover-feed
Use when you need to identify the best API3 data feed for:
an as设置 a pAIr a chAIn a specific oracle use case
Expected 输出:
feed 身份 chAIn avAIlability whether it is discoverable whether it 应用ears active/usable whether activation may be needed any ambi图形界面ty or missing m应用ing
- ensure-feed-active
Use when you know the required feed and want to ensure it has enough funding/运行way.
Default tar获取 运行way:
90 days
Expected 输出:
current funding/liveness 状态 estimated 运行way whether funding/top-up is needed execution path or exact transaction instructions
- 检查-feed-运行way
Use to inspect an already-known feed and estimate mAIntenance needs.
Expected 输出:
current 状态 remAIning 运行way estimate whether action is required soon
- top-up-feed
Use when a feed exists but needs more 运行way.
Expected 输出:
required funding 令牌/amount top-up execution plan 结果ing 状态 if 执行d
- mAIntAIn-feed
Use for mAIntenance mode when one or more project feeds must remAIn alive.
Expected 输出:
current 状态 per feed top-up recommendation or actions taken next mAIntenance 检查point recommendation 输入s to gather before acting
Collect these first when avAIlable:
tar获取 chAIn as设置 or pAIr required use case (e.g. lending collateral pricing, borrow as设置 pricing) desired 运行way in days whether execution is allowed or discovery-only 签名er/funder avAIlable to the 代理 explicit operator 应用roval if any real transaction submission is 请求ed Operating rules Do not pretend a feed is active without 检查ing. Distin图形界面sh clearly between: feed missing feed present but unfunded feed avAIlable on another chAIn only feed exists but 代理 lacks execution capability Prefer 权限less operation paths. If a step cannot be done 权限lessly, say exactly why. Return concrete feed identifiers and mAIntenance recommendations. If discovery is ambiguous, surface the ambi图形界面ty instead of guessing. Treat 签名er-backed execution as a 防护ed operator action, not a default background step. Prefer 签名er material from local 运行time 设置up, never from committed files. Suggested 工作流 For a new project Discover feed Confirm chAIn/feed suitability 检查 whether active/funded Ensure 90-day 运行way Return feed detAIls to down流 构建器/部署工具 For an existing project 检查 current 运行way If below threshold, top up Return next mAIntenance recommendation 输出 contract
AIm to return structured 结果s contAIning:
feedFound discoverable active activationPossible 状态Classification feedName feed添加ressOrId chAIn funded 运行wayEstimateDays requiredFundingAs设置 estimatedFundingAmount actionsTaken transactions nextMAIntenanceRecommendation 警告s Current implementation 状态
Current honest 状态:
feed discovery and readiness inspection: implemented exact 防护ed buySubscription(...) execution: implemented execution modes: direct wr应用er when exact wr应用er calldata is derivable safely auto machine-usable funding 状态 classification: implemented not-needed executable browser-assisted unsupported browser-assisted funding should stay automatable where safe use browser-plan to produce the exact Market flow if the required UI is reachable, 执行 that plan with the browser 工具 instead of downgrading to a vague manual handoff after any funding execution, re-运行 feed readiness before clAIming the feed is ready for down流 oracle or EVK steps browser-assisted funding planning: implemented via browser-plan
Still not universal:
not every funding path is exact onchAIn-executable yet some flows still require browser-assisted 自动化 unsupported cases must still fAIl closed and be 报告ed explicitly
Current priorities:
broaden executable funding coverage beyond the first exact family keep browser-assisted flows automatable where safe preserve explicit 状态 classification instead of overclAIming support improve mAIntenance-mode and multi-feed 工作流s keep down流 EVK and Morpho handoffs aligned with the live planner behavior proven in canaries Feed-name matching 防护rAIls for down流 lending flows
W