# 1.2 Barriers to API providers operating oracles

During our work on Honeycomb API Marketplace in the past two years, we communicated with API providers extensively and observed the following barriers to oracle onboarding and operation:

1. Traditional API providers are typically not more familiar with blockchain tech- nologies than the general public. This applies even for the ones that curate

<figure><img src="https://2736089543-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2oRqBXGjY0J1dKFtDldF%2Fuploads%2FT6yHDbVhwkFFaglFqPCl%2Fimage.png?alt=media&#x26;token=d47b5128-34bc-482d-b024-b0810793d94c" alt=""><figcaption><p>Airnode is designed to be deployed once by the API provider, then not require any further maintenance.</p></figcaption></figure>

cryptocurrency market data—as their main operation is collecting data from exchange APIs, processing them, and serving the result through their own APIs—which does not require any blockchain-specific know-how. Therefore, they typically cannot readily operate an oracle node with in-house resources.

2. There is no job market for oracle node operators. Even if some API providers were to obtain the specific know-how needed by hiring the few node operators that are available, this would not be a scalable solution.
3. Operating an oracle node consumes a lot of resources in the form of man- hours and infrastructure costs. Unless one is guaranteed significant subsidies or future profits, operating an oracle node is financially infeasible.
4. Operating an oracle node requires the API provider to transact with cryptocur- rencies. Specifically, they must pay for gas costs in the native currency and receive payments in one or more cryptocurrencies. This disqualifies the vast majority of API providers due to compliance, legal and accounting reasons. In addition, any scheme that requires API providers to stake funds is categorically rejected for similar financial risk-related reasons.
