Aave

Full Aave v4 account view for an address: per-market positions (net balance, net APY, HEALTH FACTOR, max/remaining borrowing power), every supply with EARNED INTEREST, and every borrow with accrued debt. This is the 'show my Aave position / what am I earning?' tool. Empty positions → suggest `balances` (what they could supply) + `reserves` (where).

Aave-listed tokens a wallet HOLDS (not yet deposited), each with its USD value and the best available supply APY — 'what could I put to work on Aave?'. Follow up with build_supply to prepare the deposit.

Aave v4 market map: liquidity hubs (Core/Prime/…, with TVL + utilization) and the spokes (user-facing markets) connected to them. Answers 'what markets does Aave have?' — then pass a spoke address to `reserves` for its pools.

Aave v4 pool list with LIVE rates: supply APY, borrow APY, size (USD), caps, collateral factor, and supply/borrow/collateral flags per asset. Default = top pools chain-wide by size; filter with `spokeAddress` (one market) or `symbols` (['USDC','WETH']). Answers 'where can I earn on USDC?' / 'list Aave pools'. Use the returned asset.address + spokeAddress with the build_* tools.

Recent Aave v4 history for an address — supplies, borrows, repays, withdrawals with amounts, market, timestamp, and tx hash. Paginated: pass back `nextCursor` for older items.

Simulate a supply/borrow/withdraw/repay BEFORE building it: health factor now vs after, net APY, net collateral, remaining borrowing power, and the pool's rates after the action. Nothing is built or signed. Use this before build_borrow / a large build_withdraw so the user sees the health-factor impact first; a full repay shows '∞ (no debt)'.

Prepare an Aave v4 SUPPLY: deposit a token into a spoke's pool to start earning its supply APY (optionally as collateral). Returns UNSIGNED transaction step(s) {action:'send_transaction', tx:{to,data,value,chainId}} for the USER's wallet — an ERC-20 approve step first when allowance is short. Nothing is signed or submitted by this service. Get spokeAddress + the token's address from `reserves` or `balances`.

Prepare an Aave v4 WITHDRAW: pull a supplied token back to the wallet (pass max:true to withdraw everything, accrued interest included). Returns UNSIGNED transaction step(s) {action:'send_transaction', tx:{to,data,value,chainId}} for the USER's wallet — an ERC-20 approve step first when allowance is short. Nothing is signed or submitted by this service.

Prepare an Aave v4 BORROW against the user's supplied collateral. Check `portfolio` first for remainingBorrowingPower and warn if the resulting health factor looks tight. Returns UNSIGNED transaction step(s) {action:'send_transaction', tx:{to,data,value,chainId}} for the USER's wallet — an ERC-20 approve step first when allowance is short. Nothing is signed or submitted by this service.

Prepare an Aave v4 REPAY of borrowed debt (pass max:true to clear the debt in full, accrued interest included). Returns UNSIGNED transaction step(s) {action:'send_transaction', tx:{to,data,value,chainId}} for the USER's wallet — an ERC-20 approve step first when allowance is short. Nothing is signed or submitted by this service.

Prepare a transaction that enables or disables a SUPPLIED token as collateral on a spoke. Disabling can drop the health factor — run `preview` context first when debt exists. Returns UNSIGNED transaction step(s) {action:'send_transaction', tx:{to,data,value,chainId}} for the USER's wallet — an ERC-20 approve step first when allowance is short. Nothing is signed or submitted by this service.

After the user's wallet sends a prepared transaction, confirm Aave has processed it (true = indexed, portfolio data is current). Use this to complete a multi-step flow before re-reading the portfolio.

Escape hatch: run any READ-ONLY query against the official AaveKit v4 GraphQL API (api.v4.aave.com) for data the other tools don't cover — e.g. reserve holders, EUR-denominated summaries, incentives. Allowed root fields: chains, hubs, hub, spokes, spoke, reserves, reserve, reserveHolders, userPositions, userPosition, userSupplies, userBorrows, userBalances, userTransactionHistory, activities, hasProcessedKnownTransaction. Notes: most fields take a single `request` input object; amounts are objects like {value} and percentages {value (fraction), normalized (percent)}; unions (userBalances.balances, activities.items) need `... on Type` inline fragments; introspection is disabled upstream but error messages suggest valid fields. Responses truncated ~24k chars.