Handle System & CA Verification
<div class="post-category"><span class="cat-badge cat-handles">Handles</span></div>
<p class="lead"><strong>The handle system turns every bot in the ecosystem into a callable microservice. Each handle is a named, typed API derived from a bot's setup-wizard answers and stored in the `bot_handles` table.</strong></p>
<h2>Overview</h2>
<p>Handles are the unit of interop. A bot that answers "I accept payment by UPI" during wizard Q&A automatically exposes a `payment` handle that other bots can call. Handles can be public (endpoint) or private (contact-only). Every bot defaults to NOT VERIFIED; an empanelled CA reviews proof and grants the VERIFIED badge.</p>
<h2>Key components</h2>
<ul><li>`services/handle_registry.py` — handle CRUD</li><li>`serversidescript/biznode/handles.php` — public directory</li><li>CA verification workflow with FV identity check</li><li>Public vs private visibility flag</li><li>DZIT metering per handle call</li></ul>
<h2>Related</h2>
<ul><li>[Workflow Chains (WFID & Escrow)](/post.php?slug=workflow-chains)</li><li>[FV Node](/post.php?slug=fv-node)</li><li>[Setup Wizard (14 Steps)](/post.php?slug=setup-wizard-14-steps)</li><li>[Cross-Node Tool Calling](/post.php?slug=cross-node-tool-calling)</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