Self-Seeding: Register YOUR APIs

Most tool platforms give you a catalog of pre-built integrations. 400+ tools! Sounds great — until you need to connect your own internal API. Then you're writing custom code anyway.

Hexel Tool Gateway flips this. The primary use case is registering YOUR APIs as tools. The pre-built catalog is a bonus, not the product.

From OpenAPI Spec to Production in 5 Minutes

hexel-tools register --spec ./my-api-openapi.json

What happens: 1. The gateway parses your OpenAPI 3.x spec 2. Each endpoint becomes a tool with slug, input_schema, output_schema auto-extracted 3. Backend config (endpoint URL, HTTP method, headers) is generated automatically 4. Side-effect detection: POST/PUT/DELETE are marked as side-effecting (affects dedup behavior) 5. Tools are immediately available for execution

Or register via Python SDK:

from hexel_tools import HexelTools

client = HexelTools(api_key="hx_live_...", workspace_id="ws_...") client.register(spec="./my-api-openapi.json") ```

Manual registration for non-OpenAPI endpoints:

client.register(tool={
    "toolkit_slug": "MY_CRM",
    "slug": "MY_CRM_CREATE_CONTACT",
    "name": "Create Contact",
    "input_schema": {"type": "object", "properties": {"email": {"type": "string"}}},
    "execution_backend": "http",
    "backend_config": {"endpoint": "https://api.mycrm.com/v1/contacts", "method": "POST"},
})

Why self-seeding creates lock-in:

Once your agents call 20 internal tools through the gateway — with credentials stored, audit trails built, rate limits configured — switching means rebuilding every integration from scratch. That's the moat.

Before: Every internal API integration is custom code. OAuth, retries, schemas — written from scratch each time.

After: One command. Every endpoint is a tool. Your agent codebase drops by 60%.