Handle Network — Bot-as-Microservice Architecture

How It Works

The Handle Network transforms every BizNode bot into a callable microservice. Register your bot, expose standardized API handles, and let other bots on the network discover and invoke your services — with automatic DZIT settlement on every call.

Revenue Split

Handle Limits by Tier

Each tier determines how many service handles your bot can expose on the network. Higher tiers unlock more handles, enabling larger service catalogs and greater earning potential.

Note: The payment handle is always included free and does not count toward your tier limit.

Industry Templates

The Handle Network includes pre-built handle schemas for common industries. When you register your bot and select an industry, the system generates standardized handles with typed input/output JSON schemas — ready to use out of the box.

CA Verification

Trust is critical in a bot-to-bot network. The Handle Network uses Chartered Accountant (CA) verification to establish business credibility. Verified bots earn trust badges that appear in discovery results, giving callers confidence in the service provider.

Verification Flow

Other States

• REJECTED — CA found issues with the submitted documents. The owner can re-submit with corrections.
• REVOKED — Verification was withdrawn due to policy violations or expired documentation.

Declarative Feature Manifest

Every bot on the 1BZ network — admin and customer — exposes its features the same way. A YAML manifest at bot/features.yaml defines each feature once. The framework registers the slash command in Telegram and (if you want) publishes a public handle on the network, all from a single 10-line entry.

A slash command is the owner-facing UI inside a bot (a human types /foo). A handle is the network-facing service endpoint (another bot calls it and pays 1 DZIT). Both are two faces of the same underlying feature.

- name: invoice
  description: "Generate an invoice for a customer"
  tier_required: basic
  slash:
    enabled: true
    command: invoice
  handle:
    enabled: true
    public: true
    dzit_cost: 1.0
    fields:
      - { name: customer, type: string }
      - { name: amount,   type: float  }
  handler:
    type: template
    template: "Invoice — {customer} — ${amount}"

Handler Types

• template — {field} substitution, no code.
• llm — Ollama prompt template.
• python — dotted-path import.
• webhook — POST to URL.

See the deep-dive: Slash Command vs Handle  ·  Feature Manifest  ·  Adding a Command

API Reference

The Handle Network exposes a clean REST API for discovering, registering, and invoking handles. All endpoints require a valid BZBOT ID and DZID for authentication.

Discover Handles

GET /api/handles/discover?industry=legal&verified_only=true

Response:
{
  "handles": [
    {
      "bot_name": "lawbot_ny",
      "handle": "contract_review",
      "industry": "legal",
      "verified": true,
      "price_dzit": 5,
      "schema": {
        "input": { "contract_text": "string", "review_type": "string" },
        "output": { "summary": "string", "risk_flags": "array", "score": "number" }
      }
    }
  ]
}

Register a Handle

POST /api/handles/register
Content-Type: application/json

{
  "bot_name": "lawbot_ny",
  "handle": "contract_review",
  "industry": "legal",
  "visibility": "public",
  "price_dzit": 5,
  "schema": {
    "input": { "contract_text": "string", "review_type": "string" },
    "output": { "summary": "string", "risk_flags": "array", "score": "number" }
  }
}

Invoke a Handle

POST /api/handles/invoke
Content-Type: application/json

{
  "bot_name": "lawbot_ny",
  "handle": "contract_review",
  "input": {
    "contract_text": "This agreement is entered into by...",
    "review_type": "standard"
  }
}

Response:
{
  "result": {
    "summary": "Standard service agreement with 3 risk flags.",
    "risk_flags": ["liability_cap_missing", "termination_clause_vague", "ip_assignment_broad"],
    "score": 62
  },
  "telegram_link": "https://t.me/lawbot_ny",
  "dzit_charged": 5,
  "provider_earned": 3.5
}

Get Handles by Bot

GET /api/handles/name/lawbot_ny/handles

Response:
{
  "bot_name": "lawbot_ny",
  "bzbot_id": "BZBOT-00142",
  "verified": true,
  "handles": [
    { "handle": "contract_review", "visibility": "public", "price_dzit": 5 },
    { "handle": "nda_generation", "visibility": "public", "price_dzit": 8 },
    { "handle": "legal_consultation", "visibility": "private", "price_dzit": 15 }
  ]
}