NEXUS Sentiment Analysis
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a disclosed paid external sentiment-analysis API, but it gives agents a crypto/stablecoin payment workflow without clear per-use approval or spending limits.
Install only if you trust NEXUS with both your input text and payment proof. Prefer sandbox mode first, and do not allow the agent to make real crypto or stablecoin payments unless you have configured explicit approval and a spending limit.
Findings (4)
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.
An agent could spend crypto or stablecoins for sentiment-analysis requests, especially if invoked repeatedly or automatically.
The skill’s recommended workflow tells the agent to choose a payment requirement and send funds as part of normal use, but the artifact does not define approval prompts, spending limits, or recipient verification.
Price: $0.10/request ... Select a `paymentRequirement` ... Send payment to the `payTo` address for `maxAmountRequired`
Require explicit user approval before every paid request, show the amount/network/recipient, set a budget cap, and default to `sandbox_test` for trials.
Anyone with access to the payment proof may be able to use the paid service or reveal payment metadata.
The required environment value is a payment proof used to authorize service calls. This is purpose-aligned for a paid API, but it should be treated like a credential.
requires: env: [NEXUS_PAYMENT_PROOF] ... `X-Payment-Proof: <masumi_payment_id>`
Use a limited or sandbox payment proof where possible, keep it out of logs and shared prompts, and rotate it if exposed.
Sensitive text submitted for analysis will leave the local environment and be processed by the NEXUS service.
User text is sent to an external AI service for processing. This is disclosed and fits the skill’s purpose, but it crosses a data boundary.
All data is sent to `https://ai-service-hub-15.emergent.host` over HTTPS/TLS ... your input data is sent to NEXUS
Only send content you are comfortable sharing with NEXUS, and review the provider’s privacy and retention terms before use.
Users have less provenance information for deciding whether to trust the endpoint with data and payments.
The registry metadata does not provide a source repository or homepage, which makes independent verification of a paid external provider harder.
Source: unknown; Homepage: none
Verify the NEXUS service identity and terms through trusted channels before providing payment proofs or funds.