Quickstarts

Dynamo is hosted per user: you get your own core instance — a dedicated deployment we operate — and run only the open client on your machine. Your prompts and payloads never leave your machine; the instance sees metering facts only (stream ids, unit counts, amounts). The flow, end to end:

1. Request an instance — the signup form

takes a minute; provisioning is currently done by hand and you receive one email with everything in it.

1. Receive your credentials — an instance URL plus two tokens:

DYNAMO_CORE_URL, OWNER_API_TOKEN (the owner wire), and PLUGIN_WIRE_TOKEN (the metering wire the gateway plugins use).

1. Install the client — npm install @dynamoprotocol/sdk (and

@dynamoprotocol/guard if you want the one-command capped proxy).

1. Make your first capped call — Control Mode walks it.
2. Witness a halt — spend a stream past its cap and watch the protocol

answer HTTP 402, fail closed, with nothing billed past the ceiling.

Launch instances run Control Mode: the full protocol with no money anywhere — caps, per-second rate envelopes, instant revocation, EIP-712 vouchers signed by scoped session keys, checkpoints, reconciliation are all the same machinery the money rails run. Money modes exist in the protocol and are disabled at the configuration level on launch instances; they are enabled per instance when you need them, never by default:

• Testnet escrow — the same session against on-chain

vault contracts; funds are escrowed and only the rules can move them.

• Card sandbox — the same session against

card authorization-backed budgets (Stripe TEST mode): one manual-capture authorization is the funded ceiling.

The object graph — budget → streams → vouchers → settlement — is identical across all three; only the funding tag and the settlement layer differ. Code you write in Control Mode runs unchanged when a money mode is enabled on your instance.