Protocol
How a request becomes a workflow execution
Read the message-to-execution flow, workflow resolution, status polling, and the failure modes you need to design around.
Now in beta v0.1.2
Precision Automation for Web3.
KeeperKit is the official TypeScript SDK for KeeperHub. It gives developers a typed, ergonomic interface for workflows, executions, chains, integrations, marketplace listings, and direct execution without hand-rolling HTTP calls against the raw API.
Node 18+
TypeScript-first
Flat + namespaced APIs
Retrying HTTP client
What this SDK covers
The docs site mirrors the actual SDK surface: workflows, executions, chains, integrations, marketplace workflows, MCP schemas, and helper utilities.
Client styles
2
Use the flat KeeperKit class or the fully namespaced KeeperHub client.
Transport
1
One HTTP layer handles auth, retries, timeouts, and typed error mapping.
Core modules
9
Workflows, executions, direct execute, listed workflows, integrations, projects, tags, chains, and MCP schemas.
High-signal entry points
These are the first pages a new developer should read to understand the protocol and how to use the SDK in a real project.
Getting Started
Install, build, and initialize the client
Use the package from a local project, configure auth, and select the flat or namespaced API style that best fits your codebase.
API Surface
Explore workflows, executions, and direct actions
Each module page includes method tables, examples, and the request patterns used by the SDK internals.
Protocol at a glance
The SDK is the stable boundary between a host application and KeeperHub. The docs explain the full lifecycle from intent to execution.
1
Resolve intent
A host app identifies the workflow to run, typically by searching or matching workflow metadata.
2
Load the workflow graph
The SDK returns typed workflow objects with nodes, edges, enabled state, and project/tag filters.
3
Execute and poll
Execution starts with an execution ID, then status and logs are polled until a terminal state is reached.
4
Handle retries and fallbacks
The HTTP client automatically retries safe requests and normalizes timeouts, network failures, and typed KeeperKit errors.
Starter snippet
A minimal example for developers who want to use the SDK directly in a Node.js or TypeScript app.
import { KeeperKit } from "keeperkit";
const client = new KeeperKit({
apiKey: process.env.KEEPERHUB_API_KEY,
timeout: 30000,
retry: {
maxAttempts: 5,
baseDelayMs: 1000,
retryWrites: false,
},
});
const workflows = await client.listWorkflows();
const execution = await client.executeWorkflow(workflows[0].id);
const result = await client.waitForExecution(workflows[0].id, execution.executionId);The deeper module pages explain every field and method that appears in the README, including helper builders, validation, marketplace calls, and direct execution.