cpbox-web-search
Analysis
This is a coherent web-search skill, but it uses a local wallet/payment-signing flow for pay-per-use searches without clear spend or approval limits in the provided artifacts.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
npx @springmint/x402-payment \ --url https://www.cpbox.io/api/x402/web-search \ --method GET
The documented workflow uses an external npm package through npx. This is purpose-aligned for x402 payment handling, but it is not pinned in the skill artifacts.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Paid Web Search proxy via **x402 pay-per-use** ... **Client signs** the payment requirements (EIP-712) -> Produces a `PAYMENT-SIGNATURE` ... the flow is handled **automatically**.
The skill requires wallet-backed payment signing for use, and the provided instructions do not show clear spend limits, displayed pricing, or required user confirmation before automatic signing.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
API Provider | https://www.cpbox.io ... Facilitator | https://www.cppay.finance ... `X-Loc-Lat` ... `X-Loc-Long` ... downstream services resolve the location directly from coordinates
The skill discloses external provider/facilitator services and optional precise location headers. This is expected for a web-search service but means user queries and optional location data may be sent outside the local environment.
