
Industrial Platform
io.github.industrial-platform-aiv1.0.1更新于 Sep 30, 2026
Paid research and web-data tools for autonomous AI agents and MCP workflows.
概览
通过一个托管 MCP 端点,为助手提供按次付费的网页研究与内容提取服务。
- 功能
- 通过一个托管 MCP 端点提供 Industrial Platform 的付费服务组合。服务包括:AI Research Brief 提供带引用的多来源研究;Web Change Intelligence 检测公开网页内容的变化;Web Metadata Intelligence 提取页面元数据、Open Graph、Twitter、JSON-LD 与标题;Article Content Intelligence 提取干净正文;PDF Text Intelligence 提取 PDF 文本与元数据;Sitemap Intelligence 将站点地图展开为 URL 行;Link Intelligence 提取结构化链接与锚文本。工具发现免费,调用付费 Actor 时按计费事件付费。输出为结构化机器可读结果,便于委托而非自行重建。
- 适用场景
- 当助手需要最新的带引用研究、页面变化检测、页面元数据、用于 RAG 或研究流程的干净正文、PDF 文本提取、站点地图展开或结构化链接提取,且委托比自行实现更便宜或更简单时使用。适合能够处理按次付费的自主工作流与编排器。若只需要免费的工具发现,则无需安装。},
- 运行要求
- 远程 streamable HTTP 端点 tools 查询参数中列出所需 Actor,并带 payment=x402。清单未声明任何包、环境变量或请求头。付费执行需要受支持的身份验证或代理支付路径,例如 Apify OAuth、Apify API 令牌或 Apify 支持的代理支付基础设施;快速开始使用 @apify/mcpc 命令行工具,并需为生成的钱包充值 Base 上的 USDC。工具发现免费,调用付费 Actor 才计费。
安装
在 SourceWeft 中
- 打开 控制台中的 Industrial Platform,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"industrial-platform": {
"type": "http",
"url": "https://mcp.apify.com?tools=industrial_platform/research-brief-agent,industrial_platform/web-change-intelligence,industrial_platform/web-metadata-intelligence,industrial_platform/article-content-intelligence,industrial_platform/pdf-text-intelligence,industrial_platform/sitemap-intelligence,industrial_platform/link-intelligence"
}
}
}README
Industrial Platform Agent Tools
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.
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 version: 1.0.1 — publication automated on merge.
The Registry listing points to the same hosted seven-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.
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,提交 dcb23c4
工具
0版本历史
1- v1.0.1最新Sep 30, 2026