heyAura AI Assistant

A one-sentence summary

HeyAura is an AI assistant integrated into Web3 wallets; it can analyze assets and behavioral patterns on public blockchains, explain investment portfolios, identify DeFi opportunities, assess risks, and convert natural language commands into transaction actions that can be reviewed by users.

Tool Introduction

HeyAura is the core product launched by the AdEx team following its brand transformation in 2026; its operational focus has shifted from a decentralized advertising infrastructure to AI agents built into wallets. This product is based on the Ethereum and EVM ecosystem, with the ADX token being used for access, staking, governance, and various other functions.

As of August 23, 2026, heyAura is still in the Beta phase; its current version focuses on portfolio analysis, comparison of opportunities, risk assessment, and user-approved blockchain transactions. The official website highlights a vision of automation, but this does not mean that the current product can control wallets arbitrarily without any restrictions.

Evolution of brands and products

Current main functions

Wallet and portfolio analysis

After connecting to or entering the account address, the system retrieves public on-chain information such as the cryptocurrency balance, holding positions, transaction history, chain distribution, and the protocols in use. It can explain the composition of assets and how funds are utilized, but it does not have knowledge of off-chain assets, tax costs, or the user’s overall investment objectives.

Opportunity identification for returns

HeyAura takes into account the wallet’s background, relevant protocols, and market data to identify idle funds and potential profit opportunities, while also comparing different strategies. The yields shown can change rapidly; it is also necessary to consider factors such as smart contracts, devaluation, liquidity, locking mechanisms, and token price risks.

Position holding and risk assessment

Assistants can compare positions, analyze the exposures associated with chains and protocols, and conduct stress tests on portfolios. The risk assessments are generated based on on-chain data and models; they do not constitute audit opinions, credit ratings, or licensed investment advice.

Natural language wallet operations

Users can specify goals such as swapping, trading, or cross-chain transactions; the system is responsible for determining the appropriate path and preparing the corresponding transactions. Ultimately, it is still the wallet owner who signs and approves these transactions – the model cannot assume any losses on behalf of the user.

Exchange and cross-chain

Beta offers support for token swapping and cross-chain operations, thereby reducing the need to switch back and forth between different protocol interfaces. Users should check the chain, token contract, quantity, recipient address, slippage, routing path, bridge transfer time, and total cost.

Transactions and multi-step processes

The system can break down complex intentions into one or more steps within the blockchain, and where wallet support is available, it uses batch transactions to reduce the number of signatures required. Batch signing is more convenient; it also means that a single approval may cover multiple actions with associated risks, and it’s not possible to skip reviewing each action individually.

Position monitoring and alerts

The official website lists continuous monitoring, recurring reminders of opportunities, changes in portfolios, and risk signals as part of the automated functions. The available triggers, frequency, notification methods, and scope of operations in the background are determined by the Beta account.

Context within the wallet

HeyAura does not start with an empty chat session; instead, it provides responses by taking into account the current balance in the wallet, the user’s location, past activities, and information related to the blockchain. This more context-aware approach enables the creation of detailed profiles of financial behavior.

Hybrid interactive interface

The product supports prompt-based dialogue, while also retaining a traditional graphical interface and direct visual control. Users can engage in conversation when explanations are needed, and return to the structured interface for signing and confirming amounts.

Current and planned capabilities

Working principle

External data

The assistant provides real-time context by drawing on the Web3 application directory, DeFi data, DApp data, airdrop interfaces, and on-chain analysis tools. Disruptions in upstream interfaces, incorrect labeling, or changes in protocols can affect the recommendations; users should therefore check the protocol details and on-chain records.

Which users are it suitable for

• Multi-chain wallet users: Gain a unified understanding of assets and positions across different EVM chains.
• DeFi participants: Compare returns, risks, locking, and capital utilization efficiency.
• Crypto beginners: Understand wallet activities and transaction steps in natural language.
• Active traders: Designed for swaps, cross-chain operations, and multi-step tasks, with reduced interface switching.
• ADX holders: Gain governance, rewards, and Beta access by pledging assets.
• Wallet and Web3 Product Team: Assessing the integration of AI for analysis and execution into the products.
• Developer: Researching some open-source versions of the AURA framework as well as the paid invocation method for x402.

Scenarios that are not suitable

• Users who are reluctant to connect their wallets, expose their public addresses, or lock up their tokens.
• Those who need a bank account in fiat currency, stocks, and comprehensive offline asset management.
• Investors who require guaranteed returns, capital preservation, or licensed investment advice.
• Users who need a Bitcoin-native, non-EVM chain, with all NFT functions fully available.
• The corporate treasury operates automatically without any systems for multi-signing, access control, auditing, or approval.
• Users who wish to delegate their private keys, seed phrases, or unlimited spending authority to an AI.

Basic usage tutorial

1. Prepare a separate wallet for testing; do not use the main wallet that holds all assets to try out the Beta version.
2. Check the official contracts for ADX and stkADX as well as the current pledging pages to avoid fake tokens with the same name.
3. Pledge or hold at least 300 stkADX tokens that meet the access requirements, and document the rules for locking and unlocking them.
4. Open the official app and connect to a test wallet; avoid any pages that ask for a seed phrase or private key.
5. Have the assistant first conduct a read-only analysis of assets, positions, chain exposure, and risks, without executing any trades immediately.
6. Select a small-scale exchange or cross-chain task, and compare the recommendations of the models with the actual pricing offered by the protocols.
7. Check each step: the chain, contract, authorization, amount, slippage, fees, and recipient address.
8. The wallet signs only when all fields match, and the final result is verified in the block explorer.
9. After use, revoke unnecessary authorizations, and keep track of costs, deviations, and the steps that require manual handling.

Secure transaction review process

1. Verify the application domain name, connect to the wallet and the network, and reject signature pages sent via chats or private messages.
2. The reading assistant provides explanations, but it is necessary to verify the agreement’s official website, the contract address, and the audit status separately.
3. Determine whether the transaction is a regular authorization, an unlimited authorization, an exchange, a cross-chain operation, a pegging, or a batch call.
4. Limit the authorization level to what is required for the task, and verify that the entity to which authorization is granted is part of a formal contract.
5. Compare the minimum received amount, slippage, Gas fees, bridge fees, protocol fees, and potential price impacts.
6. When using a hardware wallet or multi-sig, ensure that all approvers see the same human-readable summary.
7. Start with a test using the minimum amount, and only after the funds have been credited and the authorization has been revoked should you gradually increase the amount.

Beta access and pricing

HeyAura does not currently have a fixed subscription price in US dollars that is made public. To access the beta version, users need to own at least 300 stkADX tokens; these tokens can be obtained by purchasing or pledgingADX, and their actual cost varies depending on market prices, transaction fees, and the conditions of pledging.

Pawning is not a free subscription.

The user still retains the assets that represent the collateralized position and may receive rewards as well as governance rights, but the funds are exposed to risks related to price fluctuations, contracts, liquidity, and exit conditions. The threshold of 300 units cannot be simply regarded as a free allowance.

The planned premium pricing

According to the official assistance information, in the future higher output levels and greater request limits may result in charges being deducted monthly from the amount pledged, while larger pledge amounts could entitle one to discounts. At present, there are no fixed rates, specific times for charging, or rules regarding refunds; therefore, this can only be considered as a plan for the future.

ADX and stkADX

Support for networks and assets

The current instructions focus on Ethereum, Layer 2 networks, and other EVM-based chains; it is possible to view ERC-20 tokens, NFTs, prices, protocol status, and historical activities. The list of specific chains, bridges, DEXs, vaults, and assets will be updated as part of the Beta version, so it is necessary to check these details within the application before using it.

Safe design

The user finally gives approval.

HeyAura can generate and prepare transactions, but actions such as swapping, cross-chain transfers, executing trades, and other similar tasks still require user approval. This process reduces the risk of AI transferring funds without authorization, but it does not prevent users from accidentally approving malicious or incorrect transactions.

A private key is not required.

Composite analysis makes use of public account addresses and on-chain data; normal use should not require the submission of private keys or seed phrases. Any page, robot, or customer service representative that asks for such secrets must be stopped immediately.

Security processing layer

The model’s outputs are subject to security screening in order to reduce the risks associated with attacks such as prompt injection. The public documentation does not provide information on coverage rates, false positive rates, or a complete threat model, and it cannot serve as a substitute for contract auditing.

Code and token auditing

The team notes thatADX and the collateral contracts have been audited by multiple institutions, and ongoing AI-assisted code review is being implemented. The audits of tokens or collateral contracts do not automatically cover the heyAura application, the underlying protocols, cross-chain bridges, or each individual transaction that is generated.

Local model direction

The team plans to keep the first level of explanation for the wallet in the user’s environment whenever possible, sending only the minimal amount of background information required by the remote system. This capability is still under development; it cannot be claimed that all data is processed locally at present.

Privacy and wallet profiling

Blockchain addresses and transactions are public information, but a comprehensive analysis of balances, positions, history, protocol preferences, risk indicators, and conversations yields a more detailed financial profile. Being public does not mean that users do not care about linking, storing, and inferring information.

The team has released guidelines on security and privacy design, but it has not provided, on the publicly available pages that have been verified, a complete list regarding data retention, model providers, conversation deletion, and sub-processors as applied to Beta versions of the application. More specific policies should be requested before connecting to the main wallet.

Financial and on-chain risks

• AI recommendations may be incorrect, outdated, or fail to take into account changes in contracts, governance, and liquidity.
• The return rate is not equal to the net profit; Gas fees, slippage, bridge fees, and exit costs also need to be deducted.
• High-return opportunities often come with risks related to smart contracts, decoupling, liquidation, and token incentives.
• Cross-chain bridges represent a separate layer of trust, and delays in fund arrival or contract vulnerabilities can lead to losses.
• Infinite token authorization leaves the balance exposed for an extended period; it is therefore necessary to limit the amount involved and revoke such authorization on a regular basis.
• Batch transactions reduce the number of signatures required, and it is also possible to approve multiple unknown calls at once.
• Price quotes may be affected by MEV, low liquidity, and market volatility.
• ADX pledging entails risks related to token prices, smart contracts, and liquidity for exiting the position.
• The inclusion of a protocol in the pre-approval list does not guarantee safety, profitability, or solvency.
• Tax and regulatory obligations vary depending on the region, transaction, and collateral incentives.

Developer API and x402

heyAura offers APIs for functions such as wallet management, and it supports the x402 Internet-based payment method. callers do not need to use traditional API keys; instead, the proxy handles the payment on a per-request basis.

Self-payment converts model errors into actual expenses; developers must set limits for single transactions, daily usage, and overall budget, restrict the accessible endpoints, and keep track of each payment along with its impact on business performance. The public documentation does not specify a uniform rate per call.

x402 access check

• Only approved agent and service accounts are allowed to initiate paid calls.
• Set the allowlist endpoints, tokens, networks, single transaction amount, and daily cumulative limit.
• Use idempotency control for retries, timeouts, and duplicate requests.
• Isolate the payment account from the main fund wallet, retaining only the necessary balance.
• Record requests, responses, on-chain payments, and the final business purpose.
• Simulate service unavailability, abnormal quotes, and payment failures before going into the production environment.

GitHub and the open-source status

The official GitHub organization has made available various repositories related to the AURA framework, the AdEx protocol, the staking interface, the MCP for transaction construction, as well as brand-related resources. The AURA repository is licensed under GPL-3.0 and includes tools for retrieving information from the blockchain, integrating LLMs, and generating basic prompts.

This represents a form of partial open source; it does not mean that the heyAura Beta website, the fully functional backend, all security rules, training data, model weights, and commercial services are all made available. Just because the brand resource repository is public does not imply that the brand materials can be used without any licensing restrictions.

Product advantages

• Suggestions are generated based on the actual on-chain details of the wallet, which makes them more aligned with the actual holdings than those provided by generic chatbots.
• Combination analysis, opportunity identification, risk comparison, and transaction preparation form a continuous workflow.
• Natural language is combined with traditional interfaces, and there are distinct entry points for the explanation and signing processes.
• The final transaction is approved by the user, and there is no need to hand over the private key to the AI.
• Designed for Ethereum and EVM multi-chain environments, it helps DeFi users avoid the need to switch between different tools.
• ADX collateralization connects Beta access, governance, and ecosystem participation.
• Some components of the AURA framework are licensed under GPL-3.0, which facilitates review and extension by developers.
• x402 provides a programmable payment pathway for proxies to purchase API capabilities on a per-use basis.

Usage restrictions and precautions

• The product is still in Beta version, and its features, access requirements, and transaction processes may change rapidly.
• Currently, access is available only to those who hold at least 300 stkADX tokens; it is not a tool that can be used freely without any requirements.
• There is no fixed price in dollars; the tokens, Gas fees, and protocol costs all fluctuate.
• NFTs, automatic receipt of airdrops, local models, and greater levels of automation are still part of the plans.
• The public page does not list all supported chains, protocols, bridges, and assets.
• AI recommendations do not guarantee returns, nor can they replace independent research and professional financial advice.
• The security processing layer cannot detect every malicious contract, incorrect address, or economic attack.
• Once the public data from wallets is aggregated, sensitive profiles are created; the details of the privacy policy still need to be confirmed.
• Local models represent the direction of development; it cannot be assumed that current inference is entirely offline.
• The audit of ADX contracts does not mean that the heyAura application and all external protocols have undergone the same level of auditing.
• Partial open source does not mean a complete product; the backend or model weights are not fully made available in open source format when the system is run independently.
• Automatic payment via x402 requires a strict budget; otherwise, repeated attempts by the agent may continue to consume funds.

Basic information

Frequently Asked Questions

Is heyAura free?

It cannot be simply described as free. The current beta version requires at least 300 stkADX to use, and users still have to bear the costs associated with purchasing, pledging, Gas fees, and other on-chain operations.

Will heyAura control the wallet directly?

It can analyze, prepare, and suggest actions to be carried out on the chain, but current security guidelines emphasize that swaps, cross-chain transactions, and other transactions must be approved by the user. Any process that requests private keys or seed phrases is not considered legitimate use.

What operations are supported?

The current Beta version allows for analyzing portfolios, comparing positions, identifying potential profits, and conducting stress tests to assess risks; it also enables preparation for swaps, cross-chain transactions, and regular trades. The specific protocols and chains involved must be confirmed in real time within the application.

Can it guarantee the highest return?

No. The market, agreements, liquidity, and incentives are constantly changing, and AI may fail to detect risks or use outdated data.

Are NFTs and automatic airdrops available yet?

Not all of them can be considered as already available. NFT support and automatic receipt of airdrops are still listed among future features in the Beta release notes.

Are 300 units ofADX the same as 300 units of stkADX?

They are not the same. ADX is the underlying token, while stkADX represents the pledged position in the unified pool; according to the current guidelines, one must hold 300 units of stkADX to access it, and the conversion and migration ratios are determined by the pledging interface.

Is heyAura open source?

Partially open source. The AURA framework repository is licensed under GPL-3.0, but the complete beta version of the application, as well as the backend and models, are not fully available to the public.

Are APIs provided?

It offers some API capabilities and supports x402 pay-per-use pricing. The public version does not specify a fixed price; for automatic proxy services, strict limits on expenses and endpoints must be set.

Is it suitable for connecting a main wallet?

The beta phase is better suited for starting with separate, small-scale testing wallets. Once privacy, transaction previews, the ability to revoke authorizations, and risk control have been verified, a decision can be made regarding whether to expand the range of assets supported.

Summary

HeyAura connects the understanding of wallet structures, the identification of DeFi opportunities, the explanation of risks, and the blockchain-based operations that require user approval; as a result, it operates at a level closer to the execution layer within wallets than ordinary crypto chatbots. The ADX ecosystem and certain open-source AURA frameworks further provide it with a solid Web3 technical foundation.

However, it is still in the Beta phase; access to it relies on stkADX, and full automation as well as local models have not yet been implemented. Users should treat each suggestion as a draft transaction that needs to be verified, use a small separate wallet to examine the contracts, permissions, fees, and privacy aspects one by one, before deciding whether to expand their use of this service.