The Hive Engine NFT directory is live

A Hive Engine NFT directory was a 2022 commitment that stalled when the funding period ended, and it came up again as soon as we opened this project. It's now shipped.

The Hive Engine NFT Directory API is live at hive-apis.freebeings.io/he-nft, open source (MIT) at github.com/FreeBeings-io/he-nft-directory.

What shipped

A public, read-only HTTP API serving Hive Engine NFT data that until now had no unified source:

• Balances — GET /accounts/{account}/nfts: everything an account owns or has delegated, grouped by collection.
• Collections — a browsable catalog with supply, property schemas, metadata, and mapping status per collection.
• Market state — open sell books, floor prices (per payment token and per group, because one symbol-wide floor is misleading for collections that span hundreds of rarities/types), last sale, and 30-day volume.
• Activity — a rolling 30-day feed of NFT events per account. Hive Engine itself has no working NFT history source (its RPC nodes carry no history methods, and the official history service returns no NFT data — verified live), so this is captured directly from HE blocks as they happen.
• Status — GET /status reports sync freshness, mapping coverage, and backfill progress, so you never have to guess how current the data is.

The piece wallets have actually been missing is the directory: every HE NFT collection encodes its name, image, and attributes in its own property conventions, so displaying them generically has always meant integrating projects one by one. A versioned display-mapping layer now normalizes each collection into one consistent {name, image, collection, attributes} shape, with 91 collections mapped so far after a full-catalog audit. Unmapped collections still serve their raw properties, and coverage is a published /status metric, not a promise.

Developer docs, including a quickstart, full reference, live status widget, and an in-browser try-it console, are at hive-apis.freebeings.io. The service runs against public Hive Engine RPC nodes out of the box, with strict rate-limit politeness. Anyone deploying their own instance can point it at their own HE node instead — a supported setup that gives better performance, since the polite rate limits public nodes require no longer apply.

What's next

The API surface is a pre-release draft until v1. The display-object shape, valuation semantics, and rate limits are exactly the decisions consumers should shape, not ones we'll lock alone — they stay open until the endpoints freeze, and feedback from anyone building against the API counts. Display mappings will open to community contributions (PR-based) once the format is locked.

How to help

Try it against your own account, and if your collection displays wrong, or isn't mapped yet, tell us: that's what decides which mappings we seed next.

Join the discussion, at dao.freebeings.io.

Live and let live, freely.