JETTSON.DEV · AGENTS

Example agents, ready to fork.

Three example agents. Each is a short prompt on top of a Jettson machine — fork one, point it at your data, and bring it online.

Each one is a short prompt that runs on a fresh Jettson machine. Pick the closest one to your use case, change a few lines, and run your own.

Ship from any stack.

Two SDKs, one shape. Spawn a production agent from Node or Python in three lines — no orchestration layer to assemble first.

npm i @jettson/sdk

Node.js

Typed end-to-end. Works with the full Next.js / Express / Fastify lineup. Spawn-and-poll helpers built in.

example
import { Jettson } from "@jettson/sdk";

const client = new Jettson({ apiKey: process.env.JETTSON_KEY });

const agent = await client.agents.spawn({
  task: "Find 10 plumbers in Phoenix",
});
pip install jettson

Python

Async-friendly with httpx under the hood. Same shape as the Node SDK so your team can move between stacks.

example
from jettson import Jettson

client = Jettson(api_key=os.environ["JETTSON_KEY"])

agent = client.agents.spawn(
  task="Find 10 plumbers in Phoenix",
)

Why developers ship agents faster on Jettson.

The infrastructure is the product. You write the prompt and get back an agent — Jettson handles the container, the memory, the tools, the spawn.

Read the docs

Container per agent

Each agent gets its own isolated Linux container with a persistent file system, a browser, an identity, and a tool registry — wired together at spawn time, not by you at install time.

Memory that learns

Hybrid recall fires on every spawn. The agent reads the relevant memories from prior runs before it even sees the new task — so the tenth call doesn't repeat the mistakes of the first.

console · warm_pool · examplehealthy
iad● ready

US East · Ashburn

2/3

warm / total

412ms

p50 spawn

lhr● ready

Europe · London

3/3

warm / total

488ms

p50 spawn

syd● ready

APAC · Sydney

2/3

warm / total

534ms

p50 spawn

hit rate · example

warm-first

illustrative

Built for production from day one.

Multi-region warm pool. Memory that compounds. Sixteen built-in commands across five tool families. The boring infrastructure work — done.

Sub-second spawns, anywhere

Warm pools running in iad, lhr, and syd keep containers ready. First request lands in well under a second, warm.

  • iad· US East
    412ms
  • lhr· Europe
    488ms
  • syd· APAC
    534ms

Memory that compounds

Every run extracts what matters and stores it. The next run starts with relevant recall already in context.

recall · task="..."
  • research/example.co0.92

    Prefers usage-based billing

  • coding_standards0.84

    Use early returns; avoid == null

  • support/tone0.77

    Match customer's formality level

Five tool families, zero plumbing

browser · shell · files · http · memory — 16 commands, the full kit at spawn. No SDK wiring required.

jettson.tools5 families · 16 cmds
  • jettson_browser
  • jettson_shell
  • jettson_files
  • jettson_http
  • jettson_memory

Your keys, encrypted and injected

Connect OpenAI, Anthropic, GitHub, Stripe and more. KMS-encrypted at rest, injected into the container at spawn, never logged. Agents push to your GitHub with a leak-proof token.

vault · KMS-encrypted
  • ANTHROPIC_API_KEY•••• f4a2
  • GITHUB_TOKEN•••• 9c1d
  • STRIPE_API_KEY•••• 7b6e
injected at spawn · never logged