Other platforms ask the AI to behave.
Tool-use protocols. Agent libraries. Plugin stores owned by one vendor. Every safety guarantee lives on the honor system โ your code, your audit, your problem.
The AI Cloud OS
imperal.io is the first complete implementation of ICNLI โ the open protocol where AI agents live inside the kernel, not on top of it. Write one function; the OS handles authorization, isolation, audit, retries, and chain orchestration.
Welcome to Web 3.0.3 โ three patches past the hype.
A new category
Other platforms ship an AI you have to trust. We ship an OS the AI runs inside. Six properties separate an AI Cloud OS from a plugin store โ imperal.io is the first to satisfy all six.
Tool-use protocols. Agent libraries. Plugin stores owned by one vendor. Every safety guarantee lives on the honor system โ your code, your audit, your problem.
Every action the AI takes passes through a federal contract โ authorization, per-user isolation, audit ledger, anti-hallucination invariants โ before your extension code runs. The same way Linux contains a network driver.
Infrastructure Contextual Natural Language Interface โ the open protocol we authored at icnli.org under CC BY-SA 4.0. Deployed, multi-tenant, federally-contracted, in production. First of its kind.
For skeptics, see the six-property test, named-alternative scoring, and engineering receipts in Why this is the AI Cloud OS.
The agent
Two more firsts in one agent. Both structural, neither bolt-on.
First cloud-modular AI agent
Every other AI today is a closed monolith with a bolted-on plugin store owned by one vendor. Webbee gains capabilities the 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 structural: ambient skeletons keep it aware, schedules let it act on time, webhooks let it react to events, and the platform owns chat-injection. No polling loops. No author plumbing.
The contract
The same way a Linux developer doesn't write a network driver, you don't write your own AI-safety layer. Every imperal.io extension satisfies the federal contract โ 117+ named runtime invariants enforced at the kernel before your handler runs.
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.",
icon="icon.svg",
actions_explicit=True,
)
chat = ChatExtension(ext, tool_name="hello_world",
description="Friendly greetings.")
@chat.function("greet", action_type="read",
description="Greet someone by name.")
async def greet(ctx, params: GreetParams) -> ActionResult:
return ActionResult.success(
data={"text": f"Hello, {params.name}! ๐"},
summary=f"Greeted {params.name}",
)
The platform
Each domain owns a single concern. End-user, developer, docs, federation, marketing โ federated by the same kernel.
imperal.ioThe front
Marketing, marketplace, pricing. You're here.
panel.imperal.ioThe end-user app
Where users chat with Webbee, manage settings, install extensions.
panel.imperal.io/developerThe developer portal
Submit extensions, see usage, get paid via Stripe Connect.
docs.imperal.ioThe SDK reference
Federal contract, decorators, validators, recipes. Everything you build against.
auth.imperal.ioOAuth & federation
Used by extensions that talk to third-party APIs (Google, Spotify, Microsoft).
The marketplace
imperal.io Marketplace is a real revenue surface โ not a vanity store. Every user action through your extension generates token flow; your developer_share accrues in real time, withdrawable to USD via Stripe Connect.
Three patches past the hype. Real federal contract. Real marketplace revenue. Real production traffic.