SDK

Build on Maritime

Give every one of your users their own agent. One call on sign-up spins up an isolated agent on Maritime's fleet; 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

Your backend calls the SDK; Maritime runs an isolated agent for every one of your customers.

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

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

Authentication →

API keys and scopes

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 frameworks list covers the templates, and the SDK source (with runnable examples) lives at github.com/maritime-sh/maritime-sdk.