Skip to main content
Hive normalizes 13 upstream providers behind one interface. Your agent asks a question; Hive decides which source answers it and tells you which one it used.

The providers

How routing works

You do not choose a provider. Ask for a price and Hive decides whether that means CoinGecko, Codex, or CCXT based on the asset, the venue, and which sources are healthy right now. The provider field in every receipt tells you which one answered, so the same question can legitimately cite different sources on different days.

Managed keys

Hive holds the upstream credentials. You do not sign up with CoinGecko or Alchemy separately, and you do not manage their rate limits. One Hive credential covers everything in the table above.

Only official endpoints

Every provider above is accessed through its documented, official API. Hive does not scrape sites or use reverse-engineered private endpoints, which means coverage is narrower in places than it could be, and considerably more stable.

What Hive deliberately does not cover

Hive serves raw datapoints, not opinions, and skips anything your model can already search for. There are no news feeds, social sentiment scores, or trend summaries. Those are things an LLM with web access handles better, and wrapping them in an API would add a stale layer between your agent and the source.