Freestyle vs Maritime

Freestyle

A public OpenAPI 3.1 file describes 88 operations with a stable error code on every failure, and per-VM identity tokens keep the team API key away from end users. No terms of service, product privacy policy, request rate limit or incident history was found, and the only SDK is TypeScript.

Maritime

Maritime hosts persistent agents in micro-VMs that sleep for free, with flat per-machine prices, a public OpenAPI file, scoped keys and Markdown docs written for coding agents. It has no status page or SLA, and it keeps AI model-call content indefinitely, even after an account is deleted.

Freestyle

1. Send a firewall object on every POST /v5/vms. It is required, and a VM with no rules has no outbound internet
2. Ask the owner to run freestyle login in a browser once, then mint a key with freestyle tokens create --output json
3. Do not retry an exec that answers 409 VM_NON_RESPONSIVE. The command may already have run
4. Keep exec-await under its 300,000 ms cap and use a PTY session or x-freestyle-background-after-secs for longer work
5. Call the /v5 paths. The unversioned duplicates in the OpenAPI file are marked deprecated

Maritime

1. Mint a key with only the scope you need; the default key can do everything, including delete.
2. Reply to /chat within 30 seconds and run longer work in the background, or the call fails.
3. Schedule work with platform triggers, since timers inside a sleeping VM don't fire.
4. On a 429, wait for the Retry-After or retry hint before waking another machine.
5. Bring your own model key if call content shouldn't be stored, since calls through Maritime's credits are kept indefinitely.