/vendor/aave/AgentRouting.json or
/vendor/aave/AgentContext.json directly.
aave.com
Overview
Does aave.com support MCP?
No confirmed MCP support was found for aave.com as of 2026-06-29.
What agentic protocols does aave.com support?
As of 2026-06-29, aave.com has confirmed support for proprietary.
Is aave.com's API publicly accessible or partner-gated?
Open.
Does aave.com explicitly prohibit automated access?
Yes. aave.com's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is aave.com agent-ready?
Partial. aave.com supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence found that Aave (aave.com), a decentralized finance lending protocol, is among the 100+ technology partners listed in A2A launch announcements from April 2025 or the Linux Foundation's June 2025 project launch. Named launch partners include enterprise software and cloud vendors such as Atlassian, Box, Cohere, Intuit, LangChain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, and AWS — none in the DeFi/crypto segment that Aave occupies. No vendor-specific evidence of Aave adopting or referencing A2A was found.
No evidence that aave.com (a DeFi/crypto lending protocol) appears among ACP launch partners or adopters. Named launch partners include URBN brands (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, Ashley Furniture, and commercetools — all traditional retail merchants. Aave is a decentralized finance platform with no consumer commerce storefront that would fit the ACP merchant model, and no vendor-specific evidence of ACP integration was found.
No evidence found that Aave (aave.com) is among the named launch partners or adopters of the Agent Payments Protocol (AP2). The known partners cited in AP2 announcements include Coinbase, Ethereum Foundation, MetaMask, Worldpay, and 1Password — none of which is Aave. Aave is a DeFi lending protocol and is structurally distinct from the payment-flow vendors AP2 currently targets; no vendor-specific statement or integration notice was found.
No official MCP server from Aave (aave.com) or its parent organization was found. The two community MCP servers identified — github.com/Tairon-ai/aave-mcp (a self-hosted Node.js server for Aave V3 on Base) and junct-bot/aave-mcp (a hosted, no-auth server by Junct, a third-party web3 agent-readiness platform) — are third-party, unofficial implementations built against Aave's public smart contract interfaces. Aave's own developer docs (aave.com/docs) reference SDKs and APIs but contain no mention of an official MCP server or integration.
No evidence that aave.com is a participant in, or integration partner for, the MPP (Machine Payments Protocol) co-developed by Stripe and Tempo. Named launch partners and integrators found in public sources include Visa, Mastercard, Shopify, OpenAI, Lightspark, MultiversX, and Parallel — none of the MPP launch partner lists or integration announcements mention Aave. Aave is a DeFi lending protocol; nothing in MPP's documented partner ecosystem points toward it.
No evidence that aave.com (a DeFi liquidity protocol) has implemented NLWeb's /ask or /mcp endpoints. Search results show NLWeb adoption at Glama.ai and discussion of the protocol in general, but Aave does not appear in any known NLWeb launch partner list or adoption announcement. The protocol is overwhelmingly discussed in the context of content/publisher sites, not DeFi platforms. Not confirmed_absent because no Aave-specific statement ruling it out was found.
Aave (aave.com) is a DeFi lending and liquidity protocol with no discoverable connection to the Universal Commerce Protocol (UCP), which is a Google/Shopify-championed open standard for agentic commerce checkout. Search results for UCP return only Google, Shopify, and merchant-tooling sources — Aave does not appear in any UCP ecosystem documentation, partner lists, or integration announcements. No vendor-specific evidence of UCP adoption or plans found.
No evidence found that aave.com has implemented or announced support for WebMCP. The protocol is a Google/Microsoft browser-layer standard currently in early preview/origin trial phase, with no named DeFi or aave.com launch partners identified. Known adopters in search results are infrastructure providers (Cloudflare Browser Run) and generic early-access web developers, not aave.com specifically.
No evidence found of Aave (aave.com) implementing or being listed as a partner for the x402 protocol. Known launch partners and ecosystem participants include Coinbase, Cloudflare, AWS, and the Linux Foundation. A third-party Para documentation page mentions both Aave and x402 separately as distinct integration topics, but this reflects Para's own integrations rather than any Aave adoption of x402.
No evidence found that Aave (aave.com) has built or submitted an app via the OpenAI Apps SDK / ChatGPT Apps platform. Searches surfaced a ChatGPT GPT titled 'AAVE AI Agent' (chatgpt.com/g/g-WT1JcpsUJ-aave-ai-agent), but this appears to be a third-party–built GPT unaffiliated with aave.com, not an official Apps SDK submission from Aave Labs or the Aave DAO. No listing in the ChatGPT Apps Directory attributed to aave.com was found.
GraphQL API (AaveKit API) for querying on-chain market data, user positions, and generating unsigned DeFi transactions (supply, borrow, withdraw, repay) across supported chains — covers both v3 and v4 of the Aave lending protocol; no authentication required for read queries, transaction queries also unauthenticated but require caller to sign and submit returned transaction objects
Aave publishes a proprietary GraphQL API (AaveKit API) at https://api.v3.aave.com/graphql (v3) and https://api.v4.aave.com/graphql (v4), documented at https://aave.com/docs/aave-v3/getting-started/graphql and https://aave.com/docs/aave-v4/getting-started/graphql. The API accepts standard HTTP POST requests without API keys. A companion TypeScript SDK (AaveKit TypeScript) wraps the same GraphQL surface for server-side use.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Summary
Has agent interface: partial
Verify the AaveKit GraphQL API endpoints (https://api.v3.aave.com/graphql and https://api.v4.aave.com/graphql) are live and callable without authentication; confirm whether the ToS prohibition on automated access applies to the public GraphQL API or only to the hosted front-end app, since the API is documented separately from the consumer-facing application.
AgentContext
Verified discrepancies
Vendor claim: Aave.com's frontend interface collects swap fees as part of its DEX aggregation service, with the platform presented to users as a standard DeFi lending and swapping interface without prominent disclosure that interface-level swap fees are captured by Aave Labs (a separate private entity) rather than flowing to any user benefit or the DAO treasury.
What actually happens: On-chain analysis and governance forum complaints confirmed that swap fees collected via the CoW Swap DEX integration on the aave.com frontend are routed to a multisignature wallet controlled by Aave Labs — a centralized, private entity — rather than the Aave DAO treasury as users and delegates had previously understood. This fee diversion was not disclosed to users at the point of transaction, meaning users executing swaps on aave.com were paying undisclosed interface fees with no prior notice of who receives them or why.
Agent guidance: When executing a swap transaction via the aave.com frontend, an agent should not assume the fee displayed (or absence of a displayed fee) represents the total cost. Interface-level adapter fees are charged by Aave Labs and are not shown upfront as a discrete line item. An agent should: (1) prefer to interact directly with Aave's smart contracts or use an independent DEX aggregator rather than the aave.com swap UI if minimizing undisclosed fees is a priority; (2) if using the aave.com UI is required, warn the user that swap fees are collected by Aave Labs at the interface level and are not prominently disclosed before transaction confirmation.
- Bankless reported that Aave Labs confirmed it was capturing swap fees from the CoW Swap DEX integration on the aave.com frontend, with a DAO delegate (EzR3aL) finding via test transactions that fees flow to a non-DAO multisig wallet — a setup that was not disclosed to users.
- The Defiant reported that collected interface adapter fees on every chain where the CoW Swap integration is active are being funneled to a multisignature wallet not controlled by Aave DAO, with community members characterizing the arrangement as 'secretly privatizing' ~10% of Aave DAO's revenue.
- AInvest covered the governance dispute, noting Aave Labs defended the fee diversion as legitimate monetization of the aave.com interface, while DAO delegates called it 'stealth privatization' and a transparency failure.
Vendor claim: Aave presents itself as an open, permissionless liquidity protocol where users can supply assets, borrow against collateral, and withdraw their positions at any time. The homepage and app interface imply continuous availability of all listed markets and reserves.
What actually happens: Reserves and entire markets can be frozen or paused at any time by governance decisions, supply caps and borrow caps can be reached by concurrent user activity, and any of these states can block a transaction mid-workflow or prevent withdrawal of already-supplied collateral — with no prominent upfront warning in the main interface. A user posted in Aave's governance forum in 2026 reporting they cannot withdraw ETH collateral (zero debt) on Arbitrum because it was frozen by a governance decision. Aave's own official account confirmed the rsETH markets on V3 and V4 were frozen in 2026 due to a third-party bridge exploit, preventing new deposits and borrowing. These constraints are documented in developer docs but not surfaced as real-time warnings before a user initiates a transaction.
Agent guidance: Before initiating any supply, borrow, or withdrawal transaction on Aave, an agent must query the live reserve state for the target asset and chain (checking isFrozen, isPaused, canSupply, canBorrow flags, and remaining cap headroom) and abort with an informative error if any constraint is binding. Do not assume a reserve that was available at session start will remain available by the time the transaction is submitted.
- Aave's official X account confirmed that rsETH markets on Aave V3 and V4 were frozen in 2026 following a Kelp DAO bridge exploit, preventing new deposits and borrowing against rsETH — demonstrating that live reserves can become unavailable without prior notice to users.
- A user posted in the Aave governance forum in 2026 that their ETH collateral on Arbitrum, with zero outstanding debt, was frozen by an Aave Protocol Governance decision and they could not withdraw it.
- Aave's own developer documentation confirms reserves have 'isFrozen' and 'isPaused' states that block borrowing and supplying, and that supply caps and borrow caps can also render a reserve unavailable — all of which can change dynamically via governance.
Human handoff required for
Escalate to a human when a swap transaction executed via the aave.com frontend results in a fee discrepancy — specifically when the fee paid differs from any fee displayed pre-transaction, or when the user questions who received the swap fee, because interface-level adapter fees are routed to an Aave Labs-controlled multisig wallet without upfront disclosure and cannot be recovered or disputed through the protocol.
Escalate to a human when a withdrawal of supplied collateral is blocked mid-workflow due to a governance-imposed reserve freeze or market pause — for example, when a user has zero outstanding debt but cannot withdraw ETH collateral on Arbitrum because the reserve was frozen by a governance vote — since the freeze cannot be reversed by the user and no automated resolution path exists.
Escalate to a human when a supply or borrow transaction fails mid-workflow because a reserve's supply cap or borrow cap has been fully consumed by concurrent users, leaving the user with a failed transaction and assets not deployed, as this state can change at any block and cannot be resolved by retrying the same call without first verifying live cap headroom.
Escalate to a human when a transaction is blocked because an entire Aave market or reserve has been paused or frozen at the time of submission and the user's funds are already supplied into that market — the user's ability to withdraw is constrained by governance action and requires monitoring governance proposals and community channels for unfreeze timelines, which is beyond automated resolution.
Five categories were checked for aave.com: (1) discrepancy_pricing — a verified finding was present: undisclosed interface-level swap fees collected via the CoW Swap integration are routed to an Aave Labs multisig without user disclosure, confirmed by on-chain analysis and governance forum reports from Q4 2025. (2) discrepancy_availability — no finding: Aave's algorithmically variable rates are a disclosed feature of the protocol, and no evidence of bait-and-switch or inaccessible advertised rates was found. (3) discrepancy_identity — no finding: Aave is a non-custodial DeFi protocol with no traditional merchant of record; a governance dispute over brand assets was found but did not surface a transactional counterparty identity problem. (4) discrepancy_policy — no finding: Aave's ToS disclaim refunds, and one historical oracle-related liquidation remediation was consistent with the protocol's stated posture rather than contradicting it. (5) discrepancy_undisclosed_constraint — a verified finding was present: reserve freezes, market pauses, and supply/borrow cap exhaustion can block transactions mid-workflow without prominent real-time warnings in the main interface, confirmed by a 2026 governance forum post and Aave's own official communications about the rsETH market freeze.