Dynamo Protocol

One parent budget, fanned out into capped, revocable, per-second allowances across a whole network of service nodes - settled by signed vouchers, enforced at the money layer.

A workflow today is rarely one caller and one API. It is a tree: an orchestrator delegates to workers, workers call tools, tools call other services. Dynamo makes that tree payable and governable as one object: the parent budget is the funded ceiling, every branch is a child allowance with its own cap, rate envelope, and instant revocation, and every metered unit of work is a cryptographically signed voucher. Revoke a branch and its whole subtree takes no new work from that instant - structurally, not by request; work proven before the revoke is settled first.

Preview

The MVP preview is v2.2.6: anyone can request access; test mode only (Stripe test mode and the Avalanche Fuji testnet). See Preview and the release notes. Request access at https://tally.so/r/aQppaZ.

Start here: a hard spending cap, in one command

npm already carries older August releases of @dynamoprotocol/guard, @dynamoprotocol/sdk, @dynamoprotocol/mcp and @dynamoprotocol/conformance-kit. The v2.2.6 preview TypeScript SDK 4.3.3 and Python SDK 1.0.0 are not on the public registry - preview users get those as private files with their credentials. The local hard-cap demo below still runs from a clone of this repository (DYNAMO_REPO is your checkout). The guard is Not in the preview yet on hosted preview cores (Control Mode locally still works):

cd "$(mktemp -d)"
pwd
export GUARD_CAP_USD=5
"$DYNAMO_REPO/quickstart/dynamo-guard/dynamo-guard" up

That is the guard (Live in Control Mode, no money anywhere): a base URL and a key with a hard dollar cap in front of an OpenAI-compatible endpoint, enforced by a local Dynamo engine. The guard runs on your machine - your prompts and completions go only to your model provider; the engine sees metering facts only. When a request no longer fits the cap the answer is HTTP 402 and the request never reaches the provider - not an alert, not a report at the end of the month. npm's @dynamoprotocol/guard is an older published edition; the clone command above is the current in-repo path for this demo. From there, the same budgets and streams run on the money modes an operator enables on an instance: stablecoin escrow on a local chain or testnet and the credit card rail in Stripe TEST mode (Live); real money is Release-gated in this release (quickstarts). No instance yet? Request one.

A counter, or a ceiling?

Spend dashboards and usage counters answer "what happened?" - after it happened. Dynamo's enforcement is a ceiling made of money: the budget IS the funded amount (in Control Mode, a ledger ceiling with the same checks), allowances are slices of it, and a unit of work that exceeds cap, rate, or a revoked allowance cannot be settled at all. The difference is not reporting quality; it is when the answer arrives - before the money moves, instead of after.

Two frames

COST - the runaway loop stops at the money layer

An agent loop that retries itself into an accelerating burn is bounded by the stream's rate envelope (Live) and stopped by the declared anomaly envelope (Preview: the verified runtime, CORE_VERIFIED=1) mid-loop, while the budget is still mostly intact - the caller is refused (HTTP 402 through a gateway plugin, 409 anomaly on the owner API), and the ledger shows exactly what was settled and why the rest was refused. make demo-47k runs it.

SECURITY - OWASP Agentic threats, mapped to money machinery

make demo-owasp maps three OWASP Agentic Security Initiative threat classes to enforcement that already exists at the settlement layer:

OWASP ASI classDynamo machinery
ASI01 - agent compromise through a delegation chainOne revoke stops the whole delegated subtree; no voucher is signed for it after the revocation (Live)
ASI02 - tool misuse / hijacked agentAnomalous burn stops at the money layer: the rate envelope (Live) and the anomaly envelope (Preview); the stop is a refusal, not a heuristic flag
ASI03 - identity & privilege abuseA leaked session key is scoped to ONE stream: foreign-stream vouchers are refused, and the stream's own cap bounds the damage (Live)

What settles, and on what facts

Settlement is verified-value settlement on objective facts: signed oracle attestations of latency, error rate, availability, unit counts, completion - never subjective quality signals. Units after an attested break-point are refunded while they are still held back. Refunds are buyer-whole-first from held funds, and no Dynamo fee is earned before its units are final (holdback & refunds). These refunds exist only where a developer offers objective terms and the user accepts them before use: AI inference itself carries no refunds, and Dynamo enforces the agreed terms without ever deciding a refund. On a core, objective terms and breach reports run on the verified runtime (Preview: CORE_VERIFIED=1 with a terms catalogue); the in-process engine runs them as a library (Live).

The tree

Every executable TypeScript sample on this site runs against a live core in make docs-samples - what you read is what runs.