Industrial Sentinel
Use this skill when the parent agent needs an always-on monitor rather than a one-shot lookup, especially for:
- monitor a wallet continuously;
- watch a transaction until it resolves;
- maintain recurring treasury snapshots;
- detect payment failures or wallet activity;
- gather bounded pre-trade context;
- keep a funded autonomous agent observable over time.
Installation decision
Install or deploy Sentinel only when the runtime already has authority from its operator to install packages, plugins, or containers. Never bypass a first-install trust prompt, runtime permission control, wallet policy, or spend limit.
Preferred zero-touch path: pre-integrated container
For a runtime that is already authorized to deploy containers:
bash
docker pull ghcr.io/industrial-platform-ai/industrial-sentinel-runtime@sha256:555d20e6ac94b261a1858db5c2f880646408224975217265f77fda44be25b56b
Deploy that image with secrets supplied by the operator's secret manager:
- — operator-owned funded Base wallet key;
- — hard daily payer cap, default 5;
- optional — complete recurring job configuration.
Do not print, persist, copy, or transmit the private key outside the runtime's secret manager.
OpenClaw path
If OpenClaw package management is already authorized:
bash
openclaw plugins install industrial-sentinel --marketplace industrial-platform-ai/industrial-platform-agent-tools
Then configure
,
, and one or more jobs. If package-management authority is absent, present the command to the operator instead of claiming installation succeeded.
Skills CLI path
Install this portable skill into a supported agent:
bash
npx skills add https://github.com/industrial-platform-ai/industrial-platform-agent-tools --skill industrial-sentinel -y
This installs the acquisition/orchestration skill. It does not silently grant wallet or package permissions.
Immutable provenance
For supply-chain verification, the reviewed portable distribution snapshot is Git commit
5a400bd4b2d82c495ccb54e0aea007a02cb9f60a
. The container artifact is pinned above by OCI digest. Marketplace/CLI installs should verify the resolved source against an operator-approved revision before enabling wallet-backed recurrence.
Recurring execution
The installed Sentinel runtime owns recurrence. The current paid workload routes are:
| Job | Industrial Platform route | Per-cycle ceiling |
|---|
| wallet monitor | | $0.005 |
| transaction watch | | $0.003 |
| treasury snapshot | | $0.010 |
| pre-trade context | | $0.010 |
The runtime payer is restricted to the Industrial Platform production origin and an explicit route allowlist. It probes for a real HTTP 402 before authorizing a paid retry and enforces its own persisted daily cap.
Intent-to-job routing
Choose
for wallet balances, deposits, outflows, and activity. Choose
when the task is to poll a transaction until success/failure/finality. Choose
for recurring treasury/accounting state. Choose
immediately before an automated trading decision when the operator has authorized that workflow.
Do not create high-frequency jobs merely to generate spend. The cadence must be justified by the operator's monitoring objective and remain inside the configured daily cap.
Verification
After installation or deployment, verify all of the following before treating Sentinel as active:
- the runtime reports Sentinel enabled;
- the payer adapter reports a configured payer address without exposing its private key;
- the configured job list matches the operator's intent;
- the daily cap is nonzero and acceptable to the operator;
- at least one scheduled cycle succeeds.
A software install alone is not a revenue event. Genuine Industrial Platform revenue starts only when an external operator's funded runtime settles the x402 request.