The Imperal SDK

Build on Imperal. Reach every user. Get paid.

Teach Webbee a new skill with a few lines of Python and join an ecosystem of 300+ extensions. Imperal sandboxes it, makes it instantly available across Webbee Panel, Telegram, Terminal CLI, and external IDEs via imperal-mcp, and pays you from 70% of every credit spent (80%+ on higher developer subscription tiers).

invoices_skill.py
Quantum SDK v6.0 · ICNLI
from imperal_sdk import ImperalApp, Context

app = ImperalApp("invoice-guardian")

@app.tool(credits=2, confirm_writes=True)
async def remind_overdue(ctx: Context, days: int = 14):
    bills = await ctx.vault.query("unpaid invoices", days=days)
    return await ctx.draft_reminders(
        to=bills,  # Webbee asks before sending
    )
$ pipx install "imperal-mcp[code]"
✓ Zero-DevOps · AGPL-3.0

One Python decorator turns your code into a global ICNLI skill - discoverable by Webbee and every connected LLM via imperal-mcp.

How it pays off

Build once. We ship it. You get paid.

Build once

Write a skill with the Python SDK - invoices, legal workflows, server automation, or analytics. One @app.tool decorator defines inputs, safety, and credit price.

We ship it to all 4 surfaces

No servers to run, no customers to chase. Imperal lists your extension alongside 300+ tools in the Marketplace and wires it into Web Panel, Telegram, Webbee Code, and Imperal MCP.

You keep from 70% of every run

Every time an agent runs your tool, you earn from 70% of the credits spent ($1 per 1,000 credits) - and 80%+ on higher developer subscription tiers - metered by the kernel and paid straight to your bank.

How payouts work

What you get

You write the skill. We handle the rest.

No servers to run

Imperal hosts and scales your skill. No deploys, no on-call, no infrastructure to babysit.

Billing handled

Usage is metered and charged for you. We collect, we pay you out, you never touch a payment form.

Global reach

Every Imperal user can find and use your skill from day one, individuals, businesses and teams.

Built on an open standard

Skills speak ICNLI, the open protocol behind Webbee, published under CC BY-SA. No lock-in to learn.

FAQ

Frequently asked questions.

What language and SDK do I use to build an Imperal extension?
Extensions are built in Python using the open-source (AGPL-3.0) `imperal-sdk` package (`pip install imperal-sdk`). A complete tool with typed schema and credit pricing takes around 20 lines of code.
How does the 70/30 developer revenue share (and 80%+ tiers) work?
You set the credit price per tool call in your manifest. Whenever any Imperal user or agent runs your tool, from 70% (70%+) of the metered credit revenue goes directly to your developer balance - with 80% and higher shares unlocked on higher developer subscription tiers - paid out via Stripe Connect.
Do I need to run my own servers or billing infrastructure?
No. Imperal hosts your extension in isolated cloud workers, injects OAuth and API secrets from the Tenant Vault at runtime, and handles metering, invoicing, and payouts automatically.
How do I connect my local IDE to Imperal while developing?
Install `imperal-mcp` (`pipx install "imperal-mcp[code]" && imperal-mcp login && imperal-mcp setup`) to give Claude Code, Cursor, or Codex CLI direct access to the Imperal SDK docs, live AST code graph, 33 free local tools, and developer tools.

Ship your first skill today.

Create a free account, read the docs, and have Webbee learning a new trick in an afternoon. You keep the keys to your code the whole way.