Imperal Docs

Imperal Cloud โ€” the AI Cloud OS where the AI runs inside the kernel, not on top

First complete implementation of the ICNLI protocol. Webbee ๐Ÿ is its native agent. Write one function; the OS handles auth, audit, isolation, retries, multi-tenant โ€” the AI cannot side-effect anything except through us.

Imperal Cloud is the AI Cloud OS where the AI runs inside the kernel โ€” not on top of it. Other platforms ask the AI to behave: tool-use protocols, agent libraries, plugin stores. We built the kernel that contains it. Every action the AI takes passes through a federal contract enforcing authorization, isolation, audit, and anti-hallucination โ€” before your extension code runs.

The world's first complete implementation of ICNLI โ€” Infrastructure Contextual Natural Language Interface, the open protocol we authored and published under CC BY-SA 4.0 that maps natural-language intent to context-aware infrastructure actions. Anyone can implement ICNLI; we are the first who shipped it as a deployed multi-tenant cloud OS.

Webbee ๐Ÿ is its native agent โ€” and it's two more firsts in one.

First cloud-modular AI agent. Every other AI agent today is a closed monolith with a bolted-on plugin store owned by one vendor. Webbee is the first AI agent that gains capabilities the same way an OS does โ€” through federally-contracted extension packages authored by anyone, installable per-user, runtime-dynamic, LLM-provider-agnostic.

First proactive AI agent by design. ChatGPT, Claude, Gemini โ€” all reactive. They wait for the user. Webbee is the first AI agent where proactive behavior is structural: ambient skeletons keep it aware, schedules let it act on time, webhooks let it react to events, and the platform owns chat-injection so the agent can speak first when something changes. No polling loops; no author plumbing.

You write one function. The OS handles authentication, per-user isolation, RBAC scopes, action-type confirmation gates, audit ledger, retries, timeouts, cancellations, long-running task delivery, multi-tenant safety, anti-hallucination invariants, and chain orchestration across extensions. The same way a Linux dev doesn't write their own network driver โ€” you don't write your own AI-safety layer.

Welcome to Web 3.0.3 โ€” three patches past the hype.

โ†’ For skeptics: Why this is the AI Cloud OS โ€” the six-property test, named-alternative scoring, engineering receipts, falsifiable claim of priority by ICNLI.

โ†’ For builders: What we built that nobody else has โ€” 20 platform-and-agent surfaces with zero precedent.

โ†’ Why Webbee is unique: Cloud-modular + proactive by design โ€” two distinct firsts neither competitor can claim.

๐Ÿ’ฐ Build extensions, earn real money

Imperal Marketplace is a real revenue surface. Every user action through your extension generates token flow โ€” your developer_share accrues in real time, withdrawable to USD via Stripe Connect.

Pick your starting line

What you can build

Install in one line

pip install imperal-sdk
my_extension/app.py
from imperal_sdk import Extension, ChatExtension, ActionResult
from pydantic import BaseModel, Field

class GreetParams(BaseModel):
    name: str = Field(description="Person to greet")

ext = Extension(
    "hello-world",
    version="1.0.0",
    display_name="Hello World",
    description="Demo extension that greets people by name with a friendly message.",
    icon="icon.svg",
    actions_explicit=True,
)

chat = ChatExtension(ext, tool_name="hello_world", description="Hello World โ€” friendly greetings.")

@chat.function("greet", action_type="read", description="Greet someone by name with a friendly message.")
async def greet(ctx, params: GreetParams) -> ActionResult:
    return ActionResult.success(
        data={"text": f"Hello, {params.name}! ๐Ÿ"},
        summary=f"Greeted {params.name}",
    )

That's a real, working extension. The LLM will call greet(name="Alex") when a user types "say hi to alex".

Where this docs site lives

You're reading docs.imperal.io โ€” the public reference for everyone building on Imperal Cloud. Sister surfaces: panel.imperal.io (end-user UI), panel.imperal.io/developer (publish + marketplace), auth.imperal.io (OAuth, federation).

Built on hard guarantees

๐Ÿ›ก๏ธ

Federal-grade

Every action passes through an audit chokepoint. Tenant isolation enforced at the web-kernel layer. Runtime invariants block PRs that weaken them.

๐Ÿงฌ

Typed by default

@chat.function uses Pydantic for parameters. The LLM gets a JSON schema, the SDK auto-validates, and a feedback loop retries when args come back wrong.

๐ŸŒ

Multi-tenant

One extension serves many tenants simultaneously. The web-kernel passes the right user_id everywhere, fail-closed.

Install / upgrade

pip install --upgrade imperal-sdk
Manifest schemav3 (federal contract v4.0)
ValidatorsV14-V22, V24, V31 all ERROR severity
Anthropic compatibilitySonnet 4.6, Haiku 4.5, Opus 4.7
OpenAI compatibilitygpt-4.1, gpt-5 family, o3, o-series
GitHubimperalcloud/imperal-sdk

For per-release migration notes see the SDK changelog.

All pages on this site

A complete map of everything documented here. Pick anything to jump in.

๐Ÿš€ Getting Started

๐Ÿง  Core Concepts

๐Ÿ› ๏ธ Guides

๐Ÿ“ SDK Reference

๐Ÿ“š Recipes

๐Ÿ“– Reference

๐ŸŽจ Components showcase

On this page