Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

ChainAware.AI

Detect risky wallet behavior

CategoryArtificial Intelligence
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect ChainAware.AI with Flows360

Detect risky wallet behavior

Use the ChainAware.AI connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and no declared triggers.

Available actions

  • Audit Wallet Address
  • Credit Score
  • Fraud Check
  • Rug Pull Check
  • Wallet Segment
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: ChainAware.AI
  • Package: @activepieces/piece-chain-aware@0.1.0
  • Exact artifact digest: sha256:cf524ce5e072b6c500cb4e048e7b2f3d2cac5ee910b768c5ef0a1279ea9b07ea
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Audit Wallet Address (auditWalletAddress), Audit a wallet address for fraud risk Classification: read.
  • Credit Score (creditScore), Get a user's credit score Classification: read.
  • Fraud Check (fraudCheck), Calculate fraud probability for a wallet address Classification: read.
  • Rug Pull Check (rugPullCheck), Calculate fraud probability for a contract address Classification: read.
  • Wallet Segment (walletSegment), Get wallet behaviour information Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects6
Supported actions6
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Audit Wallet Address Yes No Audit a wallet address for fraud risk
Credit Score Yes No Get a user's credit score
Fraud Check Yes No Calculate fraud probability for a wallet address
Rug Pull Check Yes No Calculate fraud probability for a contract address
Wallet Segment Yes No Get wallet behaviour information
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Audit Wallet Address · Read

Audit a wallet address for fraud risk

audit_wallet_address · Risk: low · Retry: safe

Inputs

  • network · string · Required
  • walletAddress · string · Required
Credit Score · Read

Get a user's credit score

credit_score · Risk: low · Retry: safe

Inputs

  • network · string · Required
  • walletAddress · string · Required
Fraud Check · Read

Calculate fraud probability for a wallet address

fraud_check · Risk: low · Retry: safe

Inputs

  • network · string · Required
  • walletAddress · string · Required
  • onlyFraud · boolean · Optional
Rug Pull Check · Read

Calculate fraud probability for a contract address

rug_pull_check · Risk: low · Retry: safe

Inputs

  • network · string · Required
  • contractAddress · string · Required
Wallet Segment · Read

Get wallet behaviour information

wallet_segment · Risk: low · Retry: safe

Inputs

  • network · string · Required
  • walletAddress · string · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the ChainAware.AI connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-chain-aware@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required ChainAware.AI connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-chain-aware@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com