
Industrial Platform
io.github.industrial-platform-aiv1.0.1Updated Sep 30, 2026
Paid research and web-data tools for autonomous AI agents and MCP workflows.
Overview
Gives an assistant paid, machine-callable web research and extraction services through one hosted MCP endpoint.
- What it does
- Exposes a portfolio of paid Industrial Platform services through a single hosted MCP endpoint. Services include AI Research Brief for cited multi-source research, Web Change Intelligence for detecting changes in public web content, Web Metadata Intelligence for page metadata, Open Graph, Twitter, JSON-LD and headings, Article Content Intelligence for clean article text, PDF Text Intelligence for PDF text and metadata, Sitemap Intelligence for expanding sitemaps into URL rows, and Link Intelligence for structured links and anchor text. Tool discovery is free; callers pay per billing event when invoking a paid Actor. Results are structured machine-readable outputs intended to be delegated to…
- When to use it
- Use when an agent needs current cited research, page-change detection, page metadata, clean article text for RAG or research pipelines, PDF text extraction, sitemap expansion or structured link extraction, and delegation is cheaper or simpler than building the capability internally. It suits autonomous workflows and orchestrators that can handle per-call payment. It is not needed if you only want free tool discovery.},
- Requirements
- Remote streamable HTTP endpoint at configured with a tools query parameter listing the desired Actors and payment=x402. No packages, environment variables or headers are declared in the manifest. Paid execution requires a supported authenticated or agentic-payment path, such as Apify OAuth, Apify API tokens or Apify-supported agentic payment infrastructure; the quick start uses the @apify/mcpc CLI and a wallet funded with USDC on Base. Tool discovery is free; calls to paid Actors are billed.
Installation
In SourceWeft
- Open Industrial Platform in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"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:
Source: README.md at commit dcb23c4
Tools
0Version history
1- v1.0.1LatestSep 30, 2026