AirnodeHub lists 35 APIs in its catalogue as of 14 September. They cover financial markets, public statistics, transport, weather and other services. That number counts catalogue entries, each of which can expose several operations. AirnodeHub catalogue
The common interface gives an application a way to discover an operation, inspect its parameters and request data. API3's consumer documentation says all current listings are free during early access. A developer should still check the operation's price before calling it, since that policy can change. Consumer documentation
Five practical workflows
| Tool to build | Listings to use | Useful output |
|---|---|---|
| Crypto market watchlist | CoinGecko, Hyperliquid | Prices, trading activity, funding history and order-book context |
| Wallet activity report | dRPC | Indexed balances and transactions across supported chains |
| Economic comparison | Eurostat, Frankfurter | Published economic observations alongside dated exchange rates |
| Natural-event tracker | USGS Earthquakes, NASA EONET | Event locations, source records and subsequent revisions |
| Commute assistant | BusMaps | Nearby stops, departures, route plans and disruption notices |
These are application ideas built around the documented operations. The catalogue supplies the data access; a developer builds the interface, calculations and saved history.
A market watchlist with context. CoinGecko's coinsMarkets operation can return prices, market capitalization, volume and 24-hour percentage changes for selected coin IDs. Hyperliquid adds funding history and order-book snapshots through fundingHistory and l2Book. Together, they could support a page explaining how trading conditions differ across assets. Each reading needs its currency and observation time. Hyperliquid's integration supports reading data; placing or cancelling orders is outside its scope. CoinGecko API definition, Hyperliquid API definition
A wallet activity report. dRPC exposes walletBalances and transactionHistory, alongside a supportedChains operation for checking indexed coverage. An application could produce a dated holdings summary and a list of recent transactions. Its coverage check matters: the chains available through raw RPC access and those indexed for wallet reports are separate questions. dRPC API definition
An economic comparison with explicit units. Eurostat's getData retrieves filtered observations, while describeDataset supplies dataset information. A GDP comparison needs the same period, indicator and unit for each country. Frankfurter's getRate can add a dated currency conversion using published reference rates. The application performs that calculation and records the rate date; the result is a reference conversion, not an executable FX quote. Eurostat observations can also be provisional or revised, so their status belongs beside the figure. Eurostat listing, Frankfurter API definition
A natural-event tracker that retains revisions. USGS's queryEvents searches earthquake records by time, location and magnitude. NASA EONET's getEvents supplies records for events such as wildfires and storms, including links to reporting sources. A tracker could save an event's identifier and successive responses, then show how its recorded location, magnitude or status changed. The comparison and storage would be application features. USGS listing, NASA EONET listing
A commute assistant with coverage checks. BusMaps combines stopsInRadius, nextDepartures, planJourney and alerts. That is enough to design a tool that finds a stop, shows departures and flags disruption. Availability depends on local operator feeds. The documented notices distinguish missing coverage from a failed route search; scheduled departures can exist even when live vehicle positions do not. BusMaps listing
One request, checked against a real response
A bounded USGS request made for this guide on 14 September searched 28 March 2025 for earthquakes of magnitude 7 or greater, ordered by magnitude and limited to one result. The endpoint returned HTTP 200 and the reviewed magnitude-7.7 Myanmar event, identified as us7000pn9s. Its response included the source link and an attestation; this check did not cryptographically verify the signature. This was one successful historical query; the other workflows above were checked against documentation. USGS event record, USGS API definition
What to preserve when building on the data
The catalogue labels 34 entries as third-party and Nodary as first-party. For a third-party listing, the signature identifies the Airnode relaying the response. It does not establish a partnership with the upstream institution. Verification checks the signature against the listed operator and binds it to the request, response and signing time. The underlying observation can have an earlier date or later be revised. Keep both dates and the original response when constructing comparisons. Catalogue, Consumer documentation, Attestation specification
Start with one bounded query and a saved result. Recurring reports need an application scheduler because Airnode currently answers requests through a pull interface. Where a listing supports responseProjection, selected fields can reduce the data passed into a language model; the Airnode still fetches the upstream response. Check each listing's live API definition for supported fields and parameters. HTTP interface
For the next implementation step, Fork Brief's response-verification guide explains the request and signature checks. Chain Minute's early-access overview covers the marketplace's access model.