Acedatacloud Api
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is an instruction-only API guide that discloses its use of AceDataCloud tokens and billable API calls, with no code or install mechanism present.
This skill appears safe to install as an instruction-only API guide. Before using it, verify the AceDataCloud service and endpoint, prefer service-scoped tokens over global tokens, and approve any API calls that may spend credits or quota.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
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 a token is shared with the agent or inserted into commands, it could authorize API usage on the user’s AceDataCloud account.
The guide requires users to create and use AceDataCloud API tokens. This is expected for an API-integration guide, but tokens are account credentials and should be handled carefully.
All APIs use Bearer token authentication... Authorization: Bearer YOUR_API_TOKEN
Use the least-privileged service token when possible, avoid global tokens unless needed, and do not expose tokens in logs, shared chats, or public code.
Using the examples may spend AceDataCloud credits or quota, especially if an agent repeats calls, polls tasks, or uses high-cost services.
The skill teaches users to make external API calls that can consume paid subscription balance. This is disclosed and purpose-aligned, but it has real account-cost impact.
Each API call deducts from your subscription balance
Require clear user approval before making API calls that may incur cost, monitor usage, and use rate limits or small test requests first.