1BZ (Main Hub)
<div class="post-category"><span class="cat-badge cat-nodes">Nodes</span></div>
<p class="lead"><strong>The 1BZ main hub at https://1bz.biz is the public front door of the ecosystem. It documents every node, exposes the NodeMonitor gateway, hosts the shared asset vault, and runs the public marketplace.</strong></p>
<h2>Overview</h2>
<p>The hub publishes onboarding, pricing, and developer references for the entire network. It also operates NodeMonitor on port 7333 for LLM access and shared Qdrant on port 6333.</p>
<h2>Key components</h2>
<ul><li>Node directory and status page</li><li>NodeMonitor LLM and KB gateway</li><li>Shared asset vault (logos, brand assets)</li><li>Public marketplace for handles and tools</li><li>Token exchange links (BZeUSD on Uniswap)</li></ul>
<h2>Related</h2>
<ul><li>[NodeMonitor Gateway](/post.php?slug=nodemonitor-gateway)</li><li>[Ecosystem Overview](/post.php?slug=ecosystem-overview)</li><li>[1BZ Governance Token](/post.php?slug=1bz-governance-token)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u