
PDF Text Extractor for AI Agents
io.github.industrial-platform-aiv1.0.2更新於 Sep 30, 2026
x402 PDF text, pages, and metadata for AI/RAG. $0.0015 per successful PDF.
概覽
讓助理透過託管的按次付費遠端端點,從公開 PDF 擷取文字、逐頁文字與中繼資料。
- 功能
- 這是一個託管的遠端 MCP 伺服器,提供 PDF 文字擷取服務:回傳 PDF 的文字、依頁面拆分的文字,以及文件的中繼資料。它是 Apify 託管的同一個 MCP 端點背後多個付費 Industrial Platform 服務之一,因此工具探索免費,只有成功擷取才計費。README 說明計費事件為 pdf-extraction,每個成功 PDF 收費 $0.0015。
- 適用情境
- 當助理需要從公開 PDF 取得乾淨文字或中繼資料,用於 RAG、研究或文件處理流程,且委外呼叫比在本地自行實作 PDF 解析更簡單時適用。它鎖定已在呼叫其他 Industrial Platform 服務的代理,或希望用單一遠端端點完成文件擷取的代理。
- 執行需求
- 需要一個指向託管 Apify 端點的遠端 MCP 用戶端,並在 tools 查詢參數中選擇此 PDF 服務。付費執行需要受支援的身分驗證或代理支付方式:Apify OAuth、Apify API 權杖,或 Apify 支援的代理支付基礎設施。README 的快速開始要求在付費呼叫前,向產生的 wallet 存入 Base 上的 USDC。需要能連線至該端點的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 PDF Text Extractor for AI Agents,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"pdf-text": {
"type": "http",
"url": "https://mcp.apify.com?tools=industrial_platform/pdf-text-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