Klaus AI
Klaus is a managed cloud hosting platform for OpenClaw AI agents, built by Usebits Inc (Y Combinator W26, San Francisco) and founded by Bailey Wickham and Robbie Thompson. Klaus provisions an isolated, pre-configured OpenClaw instance on dedicated AWS ARM compute in about five minutes, with messaging channels (Slack, Telegram, WhatsApp, iMessage, Discord), Google Workspace, browser automation via Chromium and a Chrome Browser Relay extension, AgentMail email, GitHub backup, Tailscale SSH, scheduled cron tasks, semantic memory backed by OpenRouter embeddings, and instance webhooks that let external services trigger the agent over authenticated HTTP. Model access is brokered through OpenRouter with bring-your-own-key and ChatGPT-subscription options. The platform is operated through the Klaus web dashboard and a first-party command-line client published to npm as @klausai/cli, which talks to a tRPC API at api.klausai.com and proxies an OpenAI-compatible chat-completions endpoint. Authentication is by API key or an OAuth 2.0 Device Authorization Grant (RFC 8628).
Klaus AI publishes 1 API on the APIs.io network. Tagged areas include Artificial Intelligence, AI Agents, Agent Hosting, OpenClaw, and Personal Assistant.
The Klaus AI catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Klaus AI’s developer surface includes documentation, getting-started guide, support, engineering blog, pricing, signup flow, CLI, and 16 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Klaus Platform API
The Klaus platform API at api.klausai.com is a tRPC RPC surface used by the first-party @klausai/cli command-line client to manage OpenClaw instances, agents, integrations, mode...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Klaus Ai Webhooks
ASYNCAPISecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API