Industrial Platform uses the Industrial Platform Trust Protocol (IPTP) to separate Base USDC settlement, , , and . Identity verification is never a prerequisite to an ordinary x402 purchase. Current implementation is partial; see the protocol for evidence and enforcement boundaries.
Search current x402 adoption, integrations, launches and machine-payment activity.
Zuletzt geprüft
2026-11-09
Sterne
—
Tools
—
Uptime
—
optional wallet-control verification
independent commercial attribution
demand-gated factory activation
Direct recurring x402 MCP
For recurring autonomous workloads, use the direct x402-native MCP first:
These map to the same canonical paid HTTP workloads, so importer compatibility increases without splitting HTTP settlement history across duplicate routes.
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.
Install in your agent IDE
For the lowest-friction recurring workflow, install Web Metadata + Web Change first. Both currently complete in about 3 seconds median and cost $0.01 per successful unit.
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
Service
Actor
Primary purpose
Billing event
Current price
AI Research Brief
industrial_platform/research-brief-agent
Current, cited multi-source research
research-brief-completed
$1.99
Web Change Intelligence
industrial_platform/web-change-intelligence
Detect deterministic changes in public web content
These individual entries point to the same Apify-hosted Actor tools as the portfolio bundle and improve discovery for capability-specific MCP searches.
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.
Direct x402 framework integrations
Industrial Platform also exposes a direct Base x402 gateway for autonomous callers that do not need the Apify MCP layer:
The MCP server exposes the same paid tool catalog over Streamable HTTP and performs x402 negotiation at tool-call time. Tool discovery is free; a caller wallet signs the advertised Base USDC requirement when it invokes a paid tool.
Ready-to-copy adapters and workflows are included for:
Minimal official x402 caller — official x402 client, automatic 402 → payment → retry, with a hard per-payment ceiling
Coinbase AgentKit — Base wallet + AgentKit's native x402 provider, including a dry-run-by-default 1-atomic-USDC clean-room canary
ElizaOS — native @elizaos/plugin-wallet x402 client with explicit budget controls and payment disabled by default
The examples use the caller's own funded Base wallet, negotiate x402 automatically, and preserve framework-level tool choice rather than forcing Industrial Platform calls.
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.
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:
industrial_platform~ACTOR-NAME
Example:
industrial_platform~pdf-text-intelligence
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:
Need current multi-source research with citations
→ research-brief-agent
Need to know whether a monitored page changed
→ web-change-intelligence
Need Open Graph, JSON-LD, canonical, robots, and headings
→ web-metadata-intelligence
Need clean article text for a RAG or research pipeline
→ article-content-intelligence
Need text and metadata from a public PDF
→ pdf-text-intelligence
Portfolio architecture
developer / agent / orchestrator
↓
Industrial Platform MCP
↓
specialized machine service
↓
structured result / event
↓
calling system continues workflow
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.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Industrial Platform X402 Adoption Search?
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Industrial Platform X402 Adoption Search einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Industrial Platform X402 Adoption Search?
Industrial Platform X402 Adoption Search wird über HTTP erreicht.
Wann wurde Industrial Platform X402 Adoption Search zuletzt geprüft?
Zuletzt geprüft: 2026-11-09. Search current x402 adoption, integrations, launches and machine-payment activity.