Integrations

Platforms that connect to the TPMJS registry to bring tools to their users.

Case Study
✅

Building 100+ Tools with BlocksAI

How we used domain-driven validation to ship quality at scale

When we set out to build the official TPMJS tool collection, we faced a challenge: how do you maintain quality across 100+ tools? Different categories (web scraping, data transformation, statistics, security) have different requirements. Manual review doesn't scale.

BlocksAI gave us the answer: define domain rules once, validate automatically. We created a 3,200+ line blocks.yml that captures everything a TPMJS tool should be.

106
Tools Built
9
Philosophy Principles
25+
Domain Rules
11
Categories

The 9 Principles

01

Production-ready only. No stubs, no TODOs.

02

AI SDK v6 pattern. tool() + jsonSchema() exclusively.

03

Single responsibility. One thing, exceptionally well.

04

Structured outputs. Typed, parseable by agents.

05

Explicit errors. Never silently fail.

06

Async boundaries. Proper error handling.

07

Stable dependencies. No alpha packages.

08

Deterministic. Same input, same output.

09

Single-shot. No streaming, no orchestration.

Tools by Category

Research (5)Web (10)Data (15)Documents (12)Engineering (12)Security (7)Statistics (9)Operations (7)Agents (15)Utilities (8)HTML (3)

The Result

Every tool follows the same patterns. Every tool has proper error handling. Every tool works with the AI SDK. When HLLM users browse the registry, they can trust that any tool they add will work reliably in their agent workflows.

How It All Connects

BlocksAI validates tool quality at development time. TPMJS publishes them to the registry. HLLM users discover and execute them at runtime.

Using TPMJS Tools in HLLM

1

Browse the Tool Registry

In the Agent Studio, click "Add from TPM.js Registry" to open the Tool Browser. Search by name or filter by category. See descriptions, parameters, and quality scores.

1000+ tools available • Search & filter • Category tags
2

Add to Your Agent

Click any tool to add it to your agent. HLLM automatically fetches the full schema from TPMJS—parameter types, descriptions, everything the agent needs to use it correctly.

One-click add • Full schema sync • Works with any topology
3

Configure API Keys (if needed)

Some tools need API keys (Firecrawl, etc.). Add them once in your HLLM profile—they're encrypted and automatically injected when tools execute. Your keys never leave the server.

Encrypted storage • Auto-injection • Per-user isolation
4

Execute During Runs

When your agent decides to use a tool, HLLM routes the call to the TPMJS executor. The tool runs in a Deno sandbox with your parameters and API keys. Results stream back to your agent.

Sandboxed execution • SSE streaming • Execution metrics

Explore the Tools

Browse the 100+ official tools, or publish your own to the registry.