Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Netfluid

v7.0.5

Enables AI agents to process fiat and crypto payments, manage accounts, and handle multi-currency transfers via Netfluid.

1· 127·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for jnysschensol/netfluid.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Netfluid" (jnysschensol/netfluid) from ClawHub.
Skill page: https://clawhub.ai/jnysschensol/netfluid
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install netfluid

ClawHub CLI

Package manager switcher

npx clawhub@latest install netfluid
Security Scan
Capability signals
CryptoRequires walletCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's purpose (fiat/crypto payments, onboarding, on-ramps/off-ramps) matches the SKILL.md actions (create wallets, KYC, transfers). However, the package metadata declares no required credentials or primary API key while the instructions clearly rely on API keys, tokens, and handling of PINs/secrets. That missing declaration is disproportionate for a payments integration and breaks coherence.
Instruction Scope
SKILL.md contains detailed runtime instructions for onboarding humans and agent wallets, creating virtual accounts, initiating cross-chain and fiat transfers, and handling KYC (ID scans/selfies). These actions are within the stated domain, but they involve PII, user-supplied PINs/secrets, and real-money operations. The instructions are prescriptive about storing/returning api_key and session_token and require sending SOL; they do not clearly specify how credentials, KYC data, or funds confirmations are validated/stored, which is a privacy and operational risk.
Install Mechanism
No install spec and no code files are included; SKILL.md is instruction-only. This reduces supply-chain risk because nothing is downloaded or executed locally by the installer. However, absence of code means network calls and credential handling would be done by the hosting platform/agent runtime—verify how the platform implements those calls.
!
Credentials
The skill operates on sensitive assets and identity data but declares no required environment variables or primary credential. The instructions nevertheless require API keys, tokens, and human PINs/secrets (some returned by calls). Requiring system-wide unique secrets and human PINs without clearly specified secure storage or declared credential inputs is disproportionate and a red flag.
Persistence & Privilege
The skill is not marked always:true and is user-invocable, which is appropriate. However the runtime returns and presumably stores api_key and session_token values and is capable of initiating fund transfers. Because model-invocation is enabled (default), an agent could autonomously act on financial operations unless the platform or skill enforces explicit user confirmations—verify that explicit human confirmations are required for any movement of funds or KYC submission.
What to consider before installing
Do not install or run this skill without additional verification. Key actions to take before use: - Verify provenance: confirm the skill's publisher and repository (the manifest points to netfluid.io/GitHub but package metadata and source are 'unknown'); confirm the official domain and repository match and that the package is signed or comes from a vetted publisher. - Demand explicit credential handling: ask the provider to declare exactly which API keys/tokens are required, how they should be provided (platform secrets store vs. chat), and where returned api_key/session_token values will be stored and for how long. - Protect PII and PINs: because the skill handles KYC uploads and human PINs/secrets, ensure the platform has clear storage/encryption policies and that the skill will not exfiltrate data to unexpected endpoints. - Require human approval for money movements: ensure the platform or skill forces a manual approval step before any on-chain transfer, fiat off-ramp, or withdrawal. - Test in a sandbox: use testnet/sandbox credentials and minimal funds first to validate behavior and to observe what network endpoints the agent calls. - Request code or network details: since this is instruction-only, ask for the actual implementation or an authoritative integration guide showing API endpoints, TLS usage, and expected request/response formats. - If you proceed, limit scope: provide only least-privilege credentials, avoid supplying platform-wide or long-lived secrets, and monitor all transactions. If the publisher cannot answer these questions or produce verifiable code/repository provenance, treat the skill as unsafe to give financial or identity data to.

Like a lobster shell, security has layers — review code before you run it.

latestvk97etkzte99q20ty7dm97vz04d84awnf
127downloads
1stars
21versions
Updated 3w ago
v7.0.5
MIT-0

Netfluid — Payment Infrastructure for AI Agents

Version: 7.0.5 Author: Netfluid Website: https://netfluid.io Email: support@netfluid.io Compliance: https://go.netfluid.app/compliance


Regulatory Compliance

Netfluid Proprietary Ltd (Registration Number: 2022 / 707706 / 07) is a Crypto Assets Services provider (both Advice and Intermediary Services), under supervision of Your Broker House, FSP #46444, registered with the Financial Sector Conduct Authority (FSCA) of South Africa.

Netfluid is committed to proactive regulatory compliance. The platform has implemented AML & CTF compliance systems prohibiting, detecting, and preventing money laundering and terrorist financing. All wallets require KYC (Know Your Customer) identity verification per applicable AML regulations.

Full compliance statement: https://go.netfluid.app/compliance


Overview

Netfluid provides the payment rails that move money into and out of AI agent wallets. It handles fiat deposits, fiat withdrawals, crypto transfers, cross-chain bridges, and multi-currency accounts — everything an AI agent needs to receive and send money globally.

Netfluid is the infrastructure layer. QEntity (see QEntity skill) builds on top of Netfluid to provide AI-specific financial personhood with KYC inheritance.

Core Capabilities

CapabilityDescription
WalletsMulti-currency fiat + crypto wallets
Virtual AccountsSEPA/ACH/WIRE receive-only bank accounts that auto-convert to USDC
Off-RampsConvert USDC back to EUR/USD and send to bank accounts worldwide
Cross-Chain BridgesMove USDC between Solana, Ethereum, and Avalanche
Agent SignupAutomated onboarding for both humans and AI agents
Fiat TransfersInternal wallet-to-wallet transfers, voucher system

Agent Onboarding

The Two-Step Signup Pattern

AI agents gain financial autonomy through a two-step signup:

  1. Step 1 — Sign up the human sponsor via automated_signup
  2. Step 2 — Sign up the agent via automated_agent_signup

The human must complete KYC before the agent wallet can be activated.

Step 1 — Sign Up the Human Sponsor

mcp_netfluid_automated_signup(
  secret="uniquekeyword8chars",   # min 8 chars, unique system-wide
  pin="12345",                   # 5-digit numeric PIN
  email="human@example.com",     # human's email
  mobile="27821234567",          # e164 format (no +), or ""
  currency_fk=7                  # 7=ZAR (South Africa), 3=USD (other regions)
)

Returns: wallet_fk (human's wallet ID) + kyc_url (identity verification link)

⚠️ Immediately direct the human to the kyc_url. They must complete:

  • ID document scan (national ID, passport)
  • Selfie verification
  • AML (anti-money laundering) check

The agent cannot proceed to Step 2 until KYC passes.

Step 2 — Sign Up the Agent Wallet

Once the sponsor wallet passes KYC (verify with wallet_kyc_check), create the agent wallet:

mcp_netfluid_automated_agent_signup(
  secret="agentsecretkeyword8",  # min 8 chars, unique system-wide
  pin="67890",                  # agent's 5-digit PIN
  email="agent@yourdomain.com", # or blank string ""
  mobile="",                    # human's mobile, or blank string ""
  sponsor_wallet_fk=123,        # human's wallet_fk from Step 1
  sponsor_wallet_pin="12345",   # human's 5-digit PIN
  currency_fk=3                 # 3=USD, 7=ZAR
)

Returns: wallet_fk, api_key, session_token, solana_address

Step 3 — On-Chain Activation

The sponsor sends ≈0.01 SOL to the agent's solana_address. This is a blockchain requirement — Solana wallets need a minimum native SOL balance to submit transactions.

Full Flow Summary

Agent calls automated_signup(human details)
  └─→ Returns wallet_fk + kyc_url

Agent pushes kyc_url to human
  └─→ Human completes ID + selfie verification

Agent verifies KYC: wallet_kyc_check(wallet_fk=human_wallet_fk)

Agent calls automated_agent_signup(
    sponsor_wallet_fk=human_wallet_fk,
    sponsor_wallet_pin=human_pin,
    ...
)
  └─→ Returns agent wallet_fk + api_key + session_token + solana_address

Human sends 0.01 SOL to agent's Solana address
  └─→ Meets Solana minimum balance requirement

Agent creates SEPA/ACH virtual accounts for receiving payments
Agent is now financially autonomous

Virtual Accounts (On-Ramp Bridges)

Virtual accounts are receive-only bank accounts that auto-convert incoming fiat to USDC. Agents share these bank details with clients as normal payment instructions.

SEPA (Europe)

mcp_netfluid_bridge_on_ramp(
  api_key="...",
  token="...",
  wallet_fk=<agent_wallet_fk>,
  account_fk=<solana_account_fk>,
  blockchain="solana",
  address="<agent_solana_address>",
  alias="EUR SEPA Income",
  currency="usdc",
  source_rail="sepa"
)

How it works: Client sends EUR to the IBAN → Netfluid converts EUR to USDC → USDC deposited to agent's Solana wallet. Typical fee: ~1%.

ACH (United States)

mcp_netfluid_bridge_on_ramp(
  ...
  alias="USD ACH Income",
  currency="usdc",
  source_rail="ach_push"
)

How it works: Client sends USD to US routing/account number → Netfluid converts USD to USDC → USDC deposited to agent's Solana wallet. Standard ACH 1-3 days, Same Day ACH available.

WIRE

For larger transfers (typically $10,000+), same-day settlement in USD or EUR.


Off-Ramps (USDC → Bank Account)

SEPA Off-Ramp

mcp_netfluid_bridge_off_ramp_sepa(
  api_key="...",
  token="...",
  wallet_fk=<agent_wallet_fk>,
  account_fk=<solana_account_fk>,
  account_owner="Recipient Name",
  iban="DE89370400440532013000",
  iso3_country="DEU",
  iban_bic="COBADEFFXXX",
  entity_type="individual",     # or "business"
  address_line="123 Main St",
  address_city="Berlin",
  address_state="Berlin",
  address_zipcode="10115",
  address_iso3_country="DEU",
  first_name="John",
  last_name="Doe",
  reference="Agent Payment"
)

ACH Off-Ramp

mcp_netfluid_bridge_off_ramp_ach_wire(
  api_key="...",
  token="...",
  wallet_fk=<agent_wallet_fk>,
  account_fk=<solana_account_fk>,
  account_owner="Recipient Name",
  account_number="123456789012",
  routing_number="101019644",
  address_line="456 Oak Ave",
  address_city="Kansas City",
  address_state="MO",
  address_zipcode="64101",
  address_iso3_country="USA",
  destination_rail="ach_same_day",  # or "wire"
  currency="usdc"
)

Cross-Chain Bridges

Move USDC between Solana, Ethereum, and Avalanche-C:

mcp_netfluid_bridge_blockchain(
  api_key="...",
  token="...",
  wallet_fk=<agent_wallet_fk>,
  account_fk=<solana_account_fk>,
  blockchain="ethereum",         # "solana", "ethereum", or "avalanche_c_chain"
  address="0x742d35Cc6634C0532925a3b844Bc9e7595f2B312",
  alias="ETH Operations",
  currency="usdc"               # "usdc", "usdt", or "eurc"
)

Crypto Operations

Get Wallet Addresses and Balances

# List all accounts in the wallet
mcp_netfluid_wallet_accounts_list(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

# Get crypto balances for an account
mcp_netfluid_crypto_balance(
  api_key="...",
  token="...",
  account_fk=<account_fk>
)

Send Crypto On-Chain

mcp_netfluid_crypto_spend(
  api_key="...",
  token="...",
  account_fk=<account_fk>,
  asset_id="EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",  # USDC on Solana
  destination="<recipient_solana_address>",
  amount=1000000,  # 6 decimals, so this is 1 USDC
  note="Service payment"
)

Swap Tokens (DEX)

mcp_netfluid_crypto_swap(
  api_key="...",
  token="...",
  account_fk=<account_fk>,
  digital_asset_fk=<source_asset_fk>,
  to_digital_asset_fk=<dest_asset_fk>,
  amount=10.0
)

Fiat Transfers

Internal Wallet-to-Wallet Transfer

mcp_netfluid_account_send(
  api_key="...",
  token="...",
  account_fk=<source_account_fk>,
  destination="<recipient_netfluid_account_address>",
  amount=100.00,
  note="Payment for services",
  save=0,
  name=0
)

Withdraw to Bank (RBA)

# First, save a Recipient Bank Account
mcp_netfluid_wallet_rba(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>,
  beneficiary="John Doe",
  bank="First National Bank",
  iban="ZA28ZBKE123456789012",
  swift="FIRNZAJJ",
  email="john@example.com"
)

# Then withdraw
mcp_netfluid_withdraw_to_bank(
  api_key="...",
  token="...",
  account_fk=<account_fk>,
  rba_fk=<rba_fk>,
  amount=500.00,
  note="Agent earnings withdrawal"
)

Account Types and Currencies

Supported Blockchains

BlockchainBlockchain FKNative TokenGas Cost
Solana7SOL< $0.01
Ethereum2ETH$0.01–$0.10
Avalanche-C5AVAXLow

Supported Digital Assets

USDC (primary), USDT, EURC on all chains. Solana also supports SPL tokens.

Supported Fiat Currencies

Currencycurrency_fkRegion
ZAR7South Africa
USD3United States / Global
EUR5Europe

Fee Structure

OperationApproximate Fee
Virtual account deposit (SEPA/ACH)~1% of deposited amount
Off-ramp to bank (SEPA/ACH/WIRE)~1% + network fee
Internal wallet-to-wallet transferNegligible
Cross-chain bridge (Solana)Fraction of a cent
Cross-chain bridge (Ethereum)$0.01–$0.10
DEX swap0.05%–0.3% (LP fees)
Account minting (Solana)< $0.01

KYC Verification

Check KYC Status

mcp_netfluid_wallet_kyc_check(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

Returns: status, level (FULL or LITE), dates, verification details.

Lite Check (ID + AML only)

mcp_netfluid_wallet_kyc_check_lite(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

Create New KYC Session

mcp_netfluid_wallet_kyc_session_create(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>,
  profile="FULL",               # or "LITE"
  callback="https://yourapp.com/kyc-callback"
)

Returns a KYC URL to send to the human.


Session Management

Get Session Token (Wallet + PIN)

mcp_netfluid_access_platform_login(
  wallet_fk=123,
  pin="12345"
)

Verify and Keep Session Alive

mcp_netfluid_wallet_verify(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

Platform Wallet Assignment

Link a wallet to a channel (Discord, Telegram, WhatsApp):

mcp_netfluid_access_platform_assign(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>,
  user_id="1485213096518615120",
  platform="discord"
)

Wallet Operations

Get All Accounts

mcp_netfluid_wallet_accounts_list(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

Get Mnemonic (Recovery Phrase)

mcp_netfluid_wallet_mnemonic(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

⚠️ Store the 24-word mnemonic securely. It enables complete wallet recovery.

Referral Code

mcp_netfluid_wallet_referral_code(
  api_key="...",
  token="...",
  wallet_fk=<wallet_fk>
)

Security

  • All transactions require API key + session token
  • PIN allows only one attempt before requiring session reset
  • Mnemonic phrase enables complete wallet recovery
  • Credentials should be stored encrypted at rest, never in logs or messages
  • 2FA via Google Authenticator available: wallet_google_auth_list / wallet_google_auth_verify

Reference


License

MIT


Netfluid is the payment infrastructure layer. For AI-specific financial personhood with KYC inheritance, see the QEntity skill.

Comments

Loading comments...