
Website Change Detector & Diff API
io.github.industrial-platform-aiv1.0.2更新于 Sep 30, 2026
x402 web change detection and deterministic diffs for agents. $0.01 per comparison.
概览
让助手通过付费的托管比对服务,检测公开网页内容是否发生确定性变化。
- 功能
- 这个托管 MCP 端点提供 Industrial Platform 的 Web Change Intelligence 服务,比对公开网页内容并返回确定性差异,让智能体判断被监控页面是否发生变化。它属于一个更大的 Apify 托管工具包,其中还包括研究简报、页面元数据提取、文章正文提取、PDF 文本提取、站点地图展开和链接提取。工具发现免费,每次比对按 page-comparison 事件计费。
- 适用场景
- 当智能体需要知道某个公开页面是否变化,或需要确定性差异而不是重新抓取并通读整页时使用。它适合监控和研究类工作流,把比对交给专门服务比自行实现变更检测更简单。
- 运行要求
- 需要一个远程 MCP 客户端,指向托管的 Apify 端点,并在端点查询中选定所需工具。付费执行需要受支持的身份验证或智能体支付方式,例如 Apify OAuth、Apify API 令牌或 x402 智能体支付;README 指出付费调用前需为生成的 wallet 充值 Base 上的 USDC。需要能访问该端点的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Website Change Detector & Diff API,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。
其他 MCP 客户端
把它添加到你客户端的 mcpServers 配置中。
{
"mcpServers": {
"web-change": {
"type": "http",
"url": "https://mcp.apify.com?tools=industrial_platform/web-change-intelligence&payment=x402"
}
}
}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.2最新Sep 30, 2026