Skip to main content
Tenki Cloud agents run in disposable Linux microVMs — provisioned in seconds, torn down when done.

Quick Start

1

Set the API key

TENKI_AUTH_TOKEN works too. Install the extra with pip install "praisonai[tenki]".
2

Simplest agent

3

With pip packages pre-installed


How It Works

Tenki boots a fresh Linux microVM per sandbox. Commands run through ephemeral exec; files move as base64 over the same channel. The stock image ships python3 — everything else installs on demand.

Configuration Options

Authenticate with an API key. One of the two token variables is required. ComputeConfig fields honoured by Tenki:
Only stable Tenki primitives are used: ephemeral exec and base64 file I/O. No volumes, snapshot creation, or template management from PraisonAI.

Common Patterns

Data analysis with pandas

Web scraping

Custom Tenki image


Best Practices

Tenki gives ephemeral microVMs with no template registry — ideal for short, disposable runs. Use E2B for instant pre-built templates, or Docker for local, reproducible containers.
A failed install tears the sandbox down. Don’t rely on the pip field for large dependency sets — bake them into a prebaked snapshot and boot it via metadata["tenki_image"] instead.
Always call shutdown_compute() when done, and set idle_timeout_s so an idle microVM self-terminates.
Tenki cannot express per-host allowlists. networking={"type": "unrestricted"} allows outbound; anything else (including "limited") disables it entirely.

Managed Agents

Overview of managed agent providers

E2B Cloud

Compare with the E2B sandbox provider