Clevr Pay
ReviewAudited by ClawScan on May 10, 2026.
Overview
The skill appears aligned with ClevrPay payment workflows, but it handles high-impact crypto payment flows through external APIs with weak provenance and incomplete safety boundaries.
Use this only if you can independently verify the ClevrPay/Cleanverse publisher and API domains. Before sending funds, confirm the deposit address outside the agent, require explicit approval for every registration or transaction, and review chain, token, amount, recipient, and fees carefully.
Findings (5)
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.
If combined with wallet capabilities, an agent could help initiate irreversible financial transactions without enough visible approval boundaries.
This shows the skill is intended to support high-value settlement and can be paired with wallet tooling for on-chain transactions, but the provided instructions do not show explicit guardrails such as mandatory user confirmation of chain, token, amount, recipient, and final send action.
enabling agents to complete high-value commercial transactions and then settle reliably... Use an EVM wallet skill ... used to send onchain transactions.
Require explicit user confirmation before any registration, withdrawal, transfer, or payment; display chain, token, amount, recipient, fees, and destination; and default to sandbox or read-only checks unless the user clearly requests a transaction.
Users may trust deposit addresses, registration links, or payment instructions without a reliable way to verify the publisher or official service origin.
For a skill that returns deposit addresses and guides stablecoin payment flows, missing source and homepage information makes it hard for users to verify that the skill is officially associated with the payment provider.
Source: unknown Homepage: none
Publish an official homepage/source link, verify the publisher identity, and document the expected API domains so users can independently confirm them before sending funds.
Users may not realize where wallet addresses, A-Pass lookups, or registration-link requests are being sent.
This security notice is at least incomplete: scripts/get_deposit_address.py hardcodes https://uatapi.cleanverse.com/api/skills and https://api.cleanverse.com/api/skills, and the API reference also lists those base URLs.
All API routing is handled internally based on user environment configuration... No hardcoded external URLs are exposed in user-facing instructions.
Correct the notice to explicitly disclose the sandbox and production domains, explain how environment selection works, and tell users how to verify official URLs.
Wallet addresses checked through the skill may reveal eligibility, status, or KYC-hash information to the provider or to anyone viewing the results.
The API exposes financial-identity status tied to wallet addresses, including a KYC hash. This is consistent with the ClevrPay purpose, but it is sensitive identity-related information.
Query A-Pass account information by blockchain address... tier, expiration time, status, and KYC hash
Only query addresses the user owns or is authorized to check, and avoid displaying or storing KYC-related fields unless needed.
Using the helper can disclose wallet addresses and payment-related intent to the Cleanverse API service.
The helper sends chain and wallet-address data to Cleanverse API endpoints. This is expected for the stated integration, but it is still an external data flow involving financial wallet identifiers.
PRODUCTION_URL = "https://api.cleanverse.com/api/skills" ... data = {"chain": chain.lower(), "address": address.lower()}Use sandbox for testing, disclose the external data flow clearly, and do not submit wallet or identity information unless the user trusts the provider.