Hive Developer Portal
Guide for building LLM agents, automation bots, and Cursor/MCP-style tools on Hive. Prefer protocol-compatible libraries, public HTTPS nodes for reads, and constrained signing for writes.
Who this is for
- LLM agents and coding assistants that call Hive JSON-RPC or client libraries
- Automation bots that observe chain state, fetch data, and submit transactions
- Cursor, MCP, or similar tool integrations that need a stable stack and safe key handling
Preferred stack
Use this ladder unless you have a hard dependency on a legacy client:
- WAX (
@hiveio/wax) — protocol-compatible transaction and object handling (TypeScript, C++, Python) - Beekeeper — key management and signing without exposing keys in application logic
- Workerbee (
@hiveio/workerbee) — observe, fetch, and submit automation on top of WAX and Beekeeper - DHive / Hive-JS — legacy JavaScript clients; fine for existing apps, not preferred for new agent work
| Component | Links |
|---|---|
| WAX docs | doc.openhive.network/wax |
| WAX Mintlify site | openhive-network-wax.mintlify.app |
WAX agent index (llms.txt) |
mintlify.com/openhive-network/wax/llms.txt |
| Workerbee | gitlab.syncad.com/hive/workerbee · @hiveio/workerbee |
| Beekeeper | gitlab.syncad.com/hive/beekeeper |
| SDK overview | SDK Libraries · SDK Reference |
Public HTTPS nodes
Point read-only JSON-RPC at a public HTTPS API. Known stables include api.hive.blog, api.deathwing.me, and anyx.io. Prefer the live list and health details on Hive Nodes. Do not hard-code a single endpoint in production agents; rotate or fall back when a node is unhealthy.
Minimal JSON-RPC example
curl -s --data '{"jsonrpc":"2.0","method":"condenser_api.get_dynamic_global_properties","params":[],"id":1}' https://api.hive.blog
See also condenser_api.get_dynamic_global_properties and Understanding Dynamic Global Properties.
Auth and key safety
- Prefer the posting key (or Keychain / Beekeeper-managed signing) for agent writes that only need social or
custom_jsonauthority - Never put active or owner keys in agent prompts, chat logs, CI output, or client-side source
- Budget resource credits (RC) before high-frequency broadcast; see RC API and the RC demo (Python)
- For interactive login flows, see Authentication (HiveSigner, Keychain, HiveAuth)
App data and analytics
- Use
custom_jsonoperations for application-specific payloads (id + JSON body) instead of overloading posts when you only need structured app state. Example pattern: Tic-Tac-Toe game - For read-heavy analytics agents, prefer HAF (Hive Application Framework) SQL/API access over hammering condenser endpoints. See Setup HAF API node
Portal machine-readable index
This portal publishes an agent-oriented link dump at https://developers.hive.io/llms.txt. Pair it with the WAX Mintlify llms.txt above when scaffolding Hive tooling.