
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