
Industrial Platform Treasury
io.github.industrial-platform-aiv1.0.0更新於 Oct 5, 2026
Recurring crypto treasury snapshots with balances, activity and gas state.
概覽
遠端 MCP 端點,提供付費的加密資產資金與行情工具,包括錢包監控、資金快照、價格、訂單簿與 K 線。
- 功能
- 這個託管的 Streamable HTTP 伺服器提供一組付費工具,例如 monitor_wallet、transaction_status、watch_transaction、treasury_snapshot、pretrade_context、crypto_candles、crypto_price、crypto_book、market_snapshot 與 monitor_webpage_change。工具探索免費,但呼叫付費工具時需要在呼叫當下進行 x402 協商,由呼叫方錢包簽署所宣告的 Base USDC 付款要求。同一個端點也承載網頁研究、內容擷取與變更偵測等服務組合。
- 適用情境
- 當助理需要週期性的加密資產資金快照、錢包活動與 gas 狀態、交易狀態,或價格、訂單簿、K 線等行情資料,而不想自行建置這些整合時,適合使用。它適用於可按次付費的自動化或週期性工作流程。
- 執行需求
- 需要支援 Streamable HTTP 的遠端 MCP 用戶端,並指向已發布的閘道端點。付費呼叫需要持有 USDC 的 Base 錢包以及支援 x402 的用戶端;部分整合使用 Apify OAuth 或 Apify API 權杖。清單中未宣告任何環境變數或標頭。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Industrial Platform Treasury,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"treasury": {
"type": "http",
"url": "https://x402-mcp-gateway-production.up.railway.app/mcp/treasury"
}
}
}README
Industrial Platform Agent Tools
Direct recurring x402 MCP
For recurring autonomous workloads, use the direct x402-native MCP first:
Literal recurring tool names are optimized for auto-import and delegation:
monitor_wallet, transaction_status, watch_transaction, treasury_snapshot, pretrade_context, crypto_candles, crypto_price, crypto_book, market_snapshot, and monitor_webpage_change.
These map to the same canonical paid HTTP workloads, so importer compatibility increases without splitting HTTP settlement history across duplicate routes.
Open-source integration toolkit for connecting AI agents, MCP clients, autonomous workflows, agent orchestrators, and developer applications to Industrial Platform machine-callable services.
Industrial Platform provides specialized paid utilities that other agents can discover and invoke instead of rebuilding research, monitoring, extraction, and document-processing capabilities inside every workflow.
Install in your agent IDE
For the lowest-friction recurring workflow, install Web Metadata + Web Change first. Both currently complete in about 3 seconds median and cost $0.01 per successful unit.
- Cursor: one-click install
- VS Code / GitHub Copilot: one-click install
- GitHub Copilot CLI:
copilot mcp add --transport http industrial-platform-fast-web 'https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence,industrial_platform/web-change-intelligence&payment=x402' - Claude Code:
claude mcp add --transport http industrial-platform-fast-web 'https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence,industrial_platform/web-change-intelligence&payment=x402' - Cline:
cline mcp install industrial-platform-fast-web --transport http 'https://mcp.apify.com?tools=industrial_platform/web-metadata-intelligence,industrial_platform/web-change-intelligence&payment=x402'
See INSTALL.md for the full installer matrix, recurring-use patterns, and the full portfolio endpoint.
One MCP endpoint for the full portfolio
This hosted MCP endpoint exposes the six currently runnable Industrial Platform services through one direct x402 integration. Tool discovery is free; autonomous callers pay only when invoking a paid Actor.
Current services
Live pricing and execution eligibility should be verified against Apify Store before paid execution.
Official MCP Registry
Industrial Platform is published in the official MCP Registry as:
Registry publication is automated on merge.
The Registry listing points to the same hosted six-service Apify MCP bundle used by this repository.
Individual MCP Registry entries
For search-oriented discovery, each paid service also has its own active MCP Registry entry:
These individual entries point to the same Apify-hosted Actor tools as the portfolio bundle and improve discovery for capability-specific MCP searches.
Machine-readable discovery
The repository publishes:
Service catalog
catalog.json is the portfolio-level machine-readable catalog. It contains Actor IDs, Store URLs, billing events, current prices, and common delegation targets.
MCP bundle manifest
manifests/mcp-bundle.json defines the hosted MCP endpoint and the Actors included in the bundle.
MCP client configuration
examples/mcp/remote-server.json can be used as a starting point for MCP clients that accept remote server configuration.
Direct x402 framework integrations
Industrial Platform also exposes a direct Base x402 gateway for autonomous callers that do not need the Apify MCP layer:
Machine-readable discovery:
Direct x402-native MCP:
The MCP server exposes the same paid tool catalog over Streamable HTTP and performs x402 negotiation at tool-call time. Tool discovery is free; a caller wallet signs the advertised Base USDC requirement when it invokes a paid tool.
Ready-to-copy adapters and workflows are included for:
- Minimal official x402 caller — official x402 client, automatic 402 → payment → retry, with a hard per-payment ceiling
- Coinbase AgentKit — Base wallet + AgentKit's native x402 provider, including a dry-run-by-default 1-atomic-USDC clean-room canary
- ElizaOS — native @elizaos/plugin-wallet x402 client with explicit budget controls and payment disabled by default
- LangChain / LangGraph
- CrewAI
- LlamaIndex
- SEO crawler workflow
- Crypto intelligence workflow
The examples use the caller's own funded Base wallet, negotiate x402 automatically, and preserve framework-level tool choice rather than forcing Industrial Platform calls.
Agent-to-agent paid quick start
Fund the generated wallet with USDC on Base before paid calls. Product #7 (Link Intelligence) is not included here until its public/agentic publication is confirmed.
Quick start
MCP
Configure one remote MCP server:
Compatible clients can then discover the exposed Actor tools from that server.
REST / Apify API
Every service can also be invoked directly through Apify's Actor API.
General Actor identifier form:
Example:
Do not commit API tokens, wallet credentials, secrets, or private keys to this repository.
When should an agent delegate?
A calling agent should prefer a specialized Industrial Platform service when delegation is cheaper, simpler, or operationally safer than rebuilding the capability internally.
Examples:
Portfolio architecture
Execution and monetization currently run through Apify.
Authentication and machine payments
Paid execution requires a supported authenticated or agentic-payment path.
Depending on the integration, this may use:
- Apify OAuth
- Apify API tokens
- Apify-supported agentic payment infrastructure
Store eligibility and pricing can change. Calling systems should inspect current Actor metadata before executing paid services.
Repository structure
Revenue initiative
The repository contains automation for:
- testing and deployment
- Apify runtime configuration
- pay-per-event pricing
- Store / agentic-payment eligibility
- external paid-event telemetry
- milestone issues at 1, 10, and 100 external paid events
See:
Security principles
Industrial Platform services should:
- block private/local-network fetch targets when accepting arbitrary URLs
- bound response sizes, timeouts, and concurrency
- use structured machine-readable outputs
- avoid silently fabricating unavailable data
- charge successful results rather than failed fetches where practical
- keep credentials in secret stores rather than source code
License
Integration examples and open-source code in this repository are provided under the MIT License unless otherwise noted.
Industrial Platform
Organization:
Apify namespace:
Machine-readable catalog:
來源:README.md,提交 1c5cbfc
工具
0版本歷史
1- v1.0.0最新Oct 5, 2026
