
Link Extractor for AI Agents
io.github.industrial-platform-aiv1.0.0更新於 Sep 30, 2026
x402 structured link extraction for agents. $0.0005 per successfully processed page.
概覽
一個託管型 MCP 端點,可按頁付費從網頁擷取結構化連結、錨文字以及內部/外部連結分類。
- 功能
- 這個遠端 MCP 伺服器提供 Industrial Platform 的付費連結擷取服務,回傳結構化頁面連結、錨文字、rel 標記,以及內部與外部連結分類。它屬於一個託管服務組合,同一個端點還能存取研究簡報、變更偵測、中介資料、文章正文、PDF 文字與網站地圖等工具。工具探索免費,每次成功擷取依事件計費。
- 適用情境
- 當助理需要從公開網頁取得結構化連結資料時適用,例如建立爬取或網站地圖流程、連結稽核或 RAG 管線,且委外呼叫比自己撰寫爬蟲更簡單。若只需要頁面正文或中介資料,或無法按次付費,則較不適合。
- 執行需求
- 需要一個指向託管 Apify 端點的遠端 MCP 用戶端,以及受支援的付費執行方式:Apify OAuth、Apify API 權杖,或使用 x402 代理支付並準備 Base 鏈上 USDC 錢包。需要能連線該端點的網路;不需要本機執行環境或安裝套件。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Link Extractor for AI Agents,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"link-extractor": {
"type": "http",
"url": "https://mcp.apify.com?tools=industrial_platform/link-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.0最新Sep 30, 2026