For API providers

AirnodeHub is the marketplace built to pay the original data source, and you are who it is built for.

You keep the vast majority of the revenue your API earns. For a small cut, we adapt it to an attestation-compatible form and let you host the attestation service yourself. You also get marketing from a marketplace optimized for agents and humans alike. What we earn is a small cut of what the marketplace processes, so it grows with your revenue rather than at its expense.

Why not another API marketplace

This is not a marketplace for low-value use cases. Data authenticity is a base primitive: consumers use a high-quality set of APIs and aggregators that can be transparently verified down to every single source.

Agents consume differently than people do. They discover a service by reading a machine-readable description rather than a landing page, they pay per request rather than per seat, they settle without a human in the loop, and they chain calls so one API's output becomes the next one's input. Serving them reaches a class of consumer that did not exist when your pricing page was written.

Listing an API

Getting your API onto AirnodeHub is two things: an Airnode deployed over it, and a listing on the Hub that points at it. Who runs the deployment is the decision that matters, because it decides what your listing can claim.

Who holds the key decides the badge

An Airnode signs with one identity, and whoever deploys it holds the mnemonic behind that identity. Run the Airnode over your own API and you attest to data you produced yourself, which is what first-party means and what the whole exercise is for. An Airnode run by anyone else attests to having relayed a response faithfully and says nothing about who produced it, so its listing carries the third-party badge and means it.

Nothing else differs between the two. The same document, the same operations, the same signature over every response. Only the address changes, and with it what a consumer can conclude from checking it.

How it works today

We do all of it. We write the OpenAPI description of your API, deploy the Airnode over it, and add the listing. Every integration on the Hub was built that way, and the ones over APIs we do not own carry the third-party badge for it. If you want your API on AirnodeHub, come and talk to us on Discord.

That is the early shape of this rather than the intended one. The point of an Airnode is that you run it and the attestation is yours, with us doing the interface work, the listing and the marketing. Getting there means publishing the library an Airnode is built from, which has not happened yet, so for now wrapping an API and hosting it arrive together.

What will not change is that listing is our decision. Running an Airnode is meant to need nobody's permission. Appearing on AirnodeHub is a claim we put our name to, so it stays curated.

Status

The marketplace lists a hardcoded registry, so a new listing is a change to the site rather than a form to fill in. Credits, API keys and payments need a backend, which is deliberately deferred, so no revenue flows yet.