A human-facing catalog of small, runnable, frontend-only demonstrations built with live AirnodeHub operations. Each example is backed by a repository README and an agent-ready prompt.
This community workspace is open to everyone and maintained by API3. It is not an official API3 product. Its projects focus on the part a normal API example often omits: how an application discovers a source, evaluates it, verifies the signed response locally, and carries the evidence forward.
This repository intentionally has no application backend. The one on-chain component, the Solana program behind Follower Proof on Solana, is deployed to devnet and called from the browser by simulation. The static Vite app in site/ calls public AirnodeHub and Airnode endpoints directly from the browser and performs EIP-191 verification locally. It does not contain a proxy, database, serverless function, secret API key, account system, webhook, or background worker. The production artifact is static and can be deployed to Cloudflare Pages or another static host.
Paid operations are never called automatically. Every demo runs without payment. Follower Proof on Solana keeps a live x402 call as an optional reference module that loads and pays only after the visitor connects a wallet and clicks, capped at $0.01 in test aUSD.
Every push to main runs tests, builds site/, and deploys site/dist to the airnodehub-community-preview Cloudflare Pages project. Each pull request from a branch in this repository receives its own temporary airnodehub-community-pr-<number> Pages project and one automatically updated preview comment. Closing or merging the pull request deletes that project and marks the preview as deleted. Fork pull requests run the checks but skip deployment so Cloudflare credentials are never exposed to untrusted code. The workflows require a CLOUDFLARE_API_TOKEN repository secret scoped to Cloudflare Pages Edit and a CLOUDFLARE_ACCOUNT_ID repository variable. Because Pages tokens are account-scoped, use a preview-only Cloudflare account for strict production isolation.
CI builds and tests only site/. The Solana program is built and tested separately with Anchor and LiteSVM; see its README.
| Use case | Outcome | Category | Airnode listings | Status |
|---|---|---|---|---|
| Trust-Aware Agent | Prefer provider-run Nodary and release ETH/USD only after local verification. | Agent safety | Nodary, CoinGecko, TickerLayer | Working |
| Asset Price Monitor | Use Nodary as the first-party reference and compare verified relays against it. | Market data | Nodary, CoinGecko, TickerLayer | Working |
| Disaster Evidence Map | Attach signed event and location inputs to every marker and alert. | Public data | NASA EONET, USGS, GeoDB | Working |
| Verified Change Tracker | Compare two signed ETH/USD snapshots and retain the receipt behind each value. | Data history | Nodary | Working |
| Follower Proof on Solana | Bring verified social stats, such as an X follower count, into a Solana program so on-chain agreements can be settled on them. | Cross-chain verification | TwitterAPI.io | Working |
All five catalog entries are runnable from the shared browser app. Future ideas remain in IDEAS.md.
- Demos — complete, visual use cases with one clear outcome.
- Browser tools — discovery, source policy, verification, or receipt handling demonstrated client-side.
- API explorations — focused interfaces that expose the live request, signed response, and derived result.
- Recipes — one reusable move with a fixture and a test.
- Agent skills — focused instructions that help agents discover, call, and verify AirnodeHub data.
- Experiments — small explorations that teach something about signed API data.
Every finished project should make five stages visible:
- Discover the operation.
- Evaluate source, signer, freshness, and payment policy.
- Call the Airnode directly.
- Verify the response locally.
- Export or preserve the underlying evidence.
An attestation proves provenance—who returned which bytes for which request and when. It does not, by itself, guarantee that the underlying real-world claim is true.
Browse the complete use-case index, inspect the proven building blocks, see the skills guide, start with the Trust-Aware Agent, or read the contribution guide.
Open to community contributions and maintained by API3. Not an official API3 product.