AirnodeHub's Morpho listing exposes read-only vault and lending-market data through a signed-response interface. A live check on October 2 returned a page of Ethereum USDC entries, demonstrating a working discovery request rather than a new token, lending product or announced partnership.
The listing's machine-readable document describes separate operations for V1 vaults, V2 vaults, V2 adapters and individual markets. Detailed queries include allocations, fees, rates and oracle addresses. It explicitly identifies the integration as operator-run, not a Morpho-operated or endorsed signer.
For the check, the request used listVaultsV2 with Ethereum chain ID 1 and USDC's contract address. The response returned ten entries and pagination metadata showing 287 matching records. Those records include both vaults and fee wrappers, so the total should not be read as 287 distinct investment vaults. Some entries had blank labels or were marked unlisted.
That makes contract identity more useful than a familiar-looking name. A dashboard could retain the chain ID and address, then request details for selected entries. It should preserve the listing status and distinguish the product types instead of presenting every result as an approved opportunity.
AirnodeHub's interface documentation explains how responses bind data to an Airnode address, request hash and timestamp. The tested response contained those fields and a signature. This check did not independently verify the signature cryptographically. Attribution is also a different question from whether a vault is safe or its future yield is predictable. A separate ETH price verification walkthrough illustrates the signature-checking step; it is not a safety assessment of these vaults.
Morpho's own API documentation describes the underlying market and vault analytics and warns that availability is not guaranteed by an SLA. An application still needs fallback behavior and a way to show when an observation was obtained.
No operation price was declared in the listing examined for this check, and the request required no payment. Developers should inspect the current document before relying on that behavior. The useful capability here is a common, traceable reading interface for DeFi data; deposits, withdrawals and trade execution remain outside this listing's scope.