Build on Maritime

Building on Maritime means giving every one of your users their own agent, sandbox or computer from your backend through the SDK. One call on sign-up spins up an isolated agent on Maritime's infrastructure; another sends it a message. You never touch a container. Maritime handles provisioning, per-customer isolation, sleep/wake, and billing.

GitHub npm · maritime-sdk PyPI · maritime

1. provision({ externalId }) Creates the customer's agent once
2. chat(id, message) Wakes it if it is asleep and sends the message
3. reply Comes back to your code

Your code provisions an agent for a customer, sends it a message, and gets the reply. A sleeping agent wakes on the message.

The whole thing: provision an agent for a customer, then chat with it. Real code, real agent, real reply. The same three lines in either language:

TypeScript

Python

provision() is idempotent: the same call on every sign-in returns the same agent.

Install

TypeScriptPython

npm install maritime-sdk

Zero dependencies. TypeScript needs Node 18+ (or Bun / Deno / edge); Python needs 3.9+.

Explore the SDK

Quickstart

Install, get a key, provision + chat with your first agent

Agents

Provision, chat, per-customer secrets, lifecycle, logs

Webhooks

Signed lifecycle events instead of polling

End users

Your users as records: policy, tokens, suspension, rebilling

Authentication

API keys and scopes

Sandboxes

Linux machines you create, run and end from code

Swarms

One command on many sandboxes at once

Computers

Linux or Windows desktops your own model drives

Networks

Internet policy, exits and private access

API reference

Every method, both languages

Examples

Real, runnable files on GitHub

Prefer raw HTTP, or another language?

Every SDK call maps 1:1 to the REST API. The framework comparison covers the templates, and the SDK source (with runnable examples) lives at github.com/maritime-sh/maritime-sdk.