
AI Web Research & Research Brief Agent
io.github.industrial-platform-aiv1.0.2更新於 Sep 30, 2026
x402 cited web research and synthesis for agents. $1.99 per completed brief.
概覽
讓助理執行付費、附引用的多來源網路研究,並取得一份綜合研究簡報。
- 功能
- 這個託管 MCP 端點提供 Industrial Platform 的付費機器可呼叫服務,列出的入口是 AI Research Brief 代理。該簡報代理執行即時、附引用的多來源網路研究並回傳綜合簡報;同一個端點也可暴露相關擷取服務,例如網頁變更偵測、頁面中介資料、文章正文、PDF 文字與網站地圖展開。工具探索免費,只有在付費服務實際執行時才計費。
- 適用情境
- 當助理需要某個主題的即時、可引用研究,或把網頁擷取工作委外比在工作流程中自行重建更便宜、更安全時使用。它鎖定能處理付費、按量計費呼叫的代理與協調器,而非一次性人工查詢。
- 執行需求
- 需要可連線託管端點 mcp.apify.com 的遠端 MCP 用戶端,並在端點查詢中選定所需工具。付費執行需要受支援的身分驗證或代理支付路徑,例如 Apify OAuth、Apify API 權杖,或使用 Base 上已儲值 USDC 錢包的 x402 代理支付。需要網路存取。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 AI Web Research & Research Brief Agent,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"research-brief": {
"type": "http",
"url": "https://mcp.apify.com?tools=industrial_platform/research-brief-agent&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
