For Agents
Score the fraud risk of a wallet, detect rug-pull risk in a contract, segment wallets by behaviour, and produce a Web3 credit score for any blockchain address.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ChainAware Enterprise API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with ChainAware Enterprise API.
Calculate the fraud probability of a wallet address from its on-chain history
Run a full behavioural audit and intent prediction for a wallet
Score the rug-pull probability of a token or contract address
GET STARTED
Use for: I need to check whether a wallet address has fraud risk before accepting a transaction, Score the rug-pull risk of a token contract before listing it, Get a behavioural profile and predicted intent for a counterparty wallet, Segment users of my dapp by behaviour quality
Not supported: Does not perform off-chain KYC, sanctions screening, or transaction broadcast — use for AI risk scoring of wallets and contracts on chain only.
ChainAware Enterprise API delivers AI-driven, real-time risk signals for Web3 wallets and contracts, scoring fraud probability for an address, predicting rug-pull risk for a smart contract, segmenting wallets by behaviour, and producing a Web3 credit score. All scoring runs against on-chain activity rather than off-chain KYC, so DeFi protocols and wallet apps can plug in without collecting identity data.
Segment a wallet into a behavioural cohort with a quality score
Generate an AI-driven Web3 credit score for a wallet
Patterns agents use ChainAware Enterprise API for, with concrete tasks.
★ Wallet Fraud Screening
Score a wallet at signup or before a high-value transaction so a dapp or exchange can step up authentication, hold funds, or block based on risk. POST /fraud/check returns a fraud probability for the address, and POST /fraud/audit returns a fuller behavioural profile and predicted intent. The scoring uses only on-chain data, so no identity collection is required.
Call POST /fraud/check with the wallet address and block the deposit flow if the returned probability exceeds 0.7
Rug Pull Pre-Listing Check
Screen a token contract before listing it on an exchange, aggregator, or wallet UI. POST /rug/pull-check returns a rug-pull probability for the contract based on deployer behaviour, liquidity patterns, and known rug signatures. Used by listing teams who need an automated first-pass filter before a manual review.
Call POST /rug/pull-check for each new token contract submitted today and queue any with probability above 0.5 for manual review
Web3 Credit Scoring for Lending
Power undercollateralised or partially-collateralised DeFi lending by feeding a borrower wallet through a behavioural credit score rather than off-chain bureau data. POST /users/credit-score returns an AI-driven trust score, and POST /segmentation/wallet-segment classifies the wallet into a behavioural cohort that can drive interest-rate tiers.
Call POST /users/credit-score for the borrower wallet, then POST /segmentation/wallet-segment to read the cohort, and pass both into the lending decision
AI Agent DeFi Risk Triage via Jentic
An agent assisting a treasury manager receives a request: 'before we send 50k USDC to this counterparty wallet, tell me if it's risky'. Through Jentic, the agent searches for a wallet-fraud-check operation, loads the input schema, and calls /fraud/check with the address using credentials from the Jentic vault. The agent returns a typed risk verdict without the developer wiring x-api-key handling.
Use Jentic to search 'check fraud risk of a wallet', load the operation backed by POST /fraud/check, and execute it with the counterparty address
5 endpoints — chainaware enterprise api delivers ai-driven, real-time risk signals for web3 wallets and contracts, scoring fraud probability for an address, predicting rug-pull risk for a smart contract, segmenting wallets by behaviour, and producing a web3 credit score.
METHOD
PATH
DESCRIPTION
/fraud/check
Calculate fraud probability for a wallet address
/fraud/audit
Full behavioural profile and intent prediction
/rug/pull-check
Score rug-pull probability for a contract
/segmentation/wallet-segment
Classify wallet into a behavioural segment
/users/credit-score
Generate Web3 credit score for a wallet
/fraud/check
Calculate fraud probability for a wallet address
/fraud/audit
Full behavioural profile and intent prediction
/rug/pull-check
Score rug-pull probability for a contract
/segmentation/wallet-segment
Classify wallet into a behavioural segment
/users/credit-score
Generate Web3 credit score for a wallet
Three things that make agents converge on Jentic-routed access.
Credential isolation
ChainAware x-api-key values are stored encrypted in the Jentic vault and injected into the request header at execution time. Agents receive scoped access only — the raw key never enters the agent's context window or prompt history.
Intent-based discovery
Agents search Jentic by intent (e.g., 'score a wallet for fraud' or 'check rug pull risk') and Jentic returns the matching ChainAware operation with its input schema, so the agent posts the right body to the right endpoint without scraping the docs.
Time to first call
Direct ChainAware integration: 2-3 hours for key handling, retry logic, and response parsing across the five endpoints. Through Jentic: under 20 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
AbuseIPDB API
Reputation scoring for IP addresses rather than wallets
Choose AbuseIPDB when scoring web traffic by IP; choose ChainAware when scoring on-chain wallet or contract behaviour
Specific to using ChainAware Enterprise API through Jentic.
What authentication does the ChainAware Enterprise API use?
The API uses an API key passed in the x-api-key request header, issued from the ChainAware profile page at chainaware.ai/profile. Through Jentic, the key is held in the Jentic vault and added to outgoing requests at execution time so it never enters the agent's prompt or context window.
Can I score a wallet's fraud risk without collecting KYC data?
Yes. POST /fraud/check and POST /fraud/audit operate against on-chain history alone, so a dapp or exchange can screen wallets at signup or before a transfer without collecting identity documents. The response includes a probability score that can drive automated blocking or step-up flows.
Does the ChainAware API detect rug pulls before launch?
POST /rug/pull-check scores a contract address using deployer behaviour, liquidity patterns, and known rug signatures, so it works on contracts that have just been deployed and on existing tokens. Teams typically use it as a first-pass filter ahead of manual review for listings.
What are the rate limits for the ChainAware Enterprise API?
Rate limits are tied to the ChainAware enterprise plan attached to your API key rather than published as a single number in the spec. Honour 429 responses with their Retry-After header, especially when batch-scoring large wallet lists.
How do I get a Web3 credit score for a wallet through Jentic?
Search Jentic for 'get a web3 credit score for a wallet', load the operation backed by POST /users/credit-score, and execute it with the wallet address. Jentic injects the x-api-key header so the agent receives a typed score and tier.
What is the difference between /fraud/check and /fraud/audit?
POST /fraud/check returns a single fraud-probability score suitable for inline decisions. POST /fraud/audit returns a fuller behavioural profile and predicted intent for the same wallet, which is more appropriate for case-by-case investigation than for high-throughput screening.