Add Dynamo to an agent framework

Not in the preview yet. This feature is built in the repository but is off in the v2.2.6 preview (test mode). Do not treat this page as available on a preview core. See ../preview.md and the release notes.

Each agent framework has its own Dynamo plugin. A plugin gives every agent in your app its own capped slice of one budget: a hand-off or a sub-agent opens a child slice that can never exceed what its parent has left, a model call that would go over its slice is refused before the model is called, one revoke stops a whole branch, and every hop is signed so you can check it offline.

None of these packages is published yet. Each installs from a clone of the repository, and each README starts with an offline quickstart (a local core in Control Mode, a scripted mock model, no provider key) and then shows the lines you add to your own app. Each framework below links to a page with the install commands, the code that wraps an agent run in a budget, and what a refusal looks like; the code on those pages is checked byte for byte against the plugin's README and example files.

Maintaining a framework, gateway, rail or platform? See the partner integration guide.

Before you start

  1. A core. Boot a local instance

in Control Mode (no money moves), or use your hosted instance. Every quickstart below boots its own local core for you.

  1. Python plugins. Use Python 3.11. Each plugin's venv, except the OpenAI

Agents SDK plugin's, is built from binary wheels pinned and hash-checked by its locks/test.txt; the OpenAI Agents SDK plugin has no lock file and installs from the package index with only its direct dependencies pinned. Upgrade pip in the new venv first from the hash-pinned scripts/py/pip-bootstrap.txt (.venv/bin/python -m pip install --require-hashes -r scripts/py/pip-bootstrap.txt): the pip bundled with Python 3.11 can refuse these locks.

  1. Node and pnpm. The repository asks for Node 22.12 or later and pnpm 9

(its engines and packageManager fields); every quickstart builds the core with them. Build a TypeScript plugin with pnpm --filter <package>... -r build.

  1. A price table. Every priced model needs a row with a source and an

as-of date; a model without one is refused. The quickstarts use mock_prices() (Python) or mockPrices() (TypeScript); with a real model pass your own table, for example quickstart/dynamo-guard/prices.json.

Credentials: owner token or scoped credentials

Most plugins connect with the owner token (DYNAMO_OWNER_TOKEN) and open the budget themselves. Some take only scoped credentials, so the agent process never holds an owner key; the operator mints them where the owner token lives:

KindMint withReaches
hookPOST /owner/v1/scoped-credentials {"kind": "hook", "budgetId": "…"}that budget only: read it, its tree and its streams' headroom, finality and authority chain; mint allowance credentials; reserve, confirm, release. It never opens, revokes, freezes or approves
delegatorPOST /owner/v1/scoped-credentials {"kind": "delegator", "streamId": "…"}that stream and its subtree: open children under that stream; read headroom, the authority chain, payment records, the payment authority and billed rows in its subtree, and the stream's status on the plugin wire; mint allowance credentials; issue payment authorizations and receipts

The answer carries the secret once (dsc1.hook.…, dsc1.delegator.…). A call outside its scope answers credential_scope. A delegator credential expires 24 hours after it is minted, or after expiresInSeconds (60 seconds to 30 days, Dynamo-Version 1.9.0), and never later than its stream's or budget's own expiry; after that it answers 401. To keep going, mint a new one. Clients pinned at 1.9.0 see expiresAt on every credential. A third kind, payee, is for a payee itself (its /payee/v1/* routes and meters on streams that pay it) and is minted only with the payee's own fresh signature; no plugin on these pages uses it.

Funding modes

What every plugin on these pages does today:

Control Mode budget: every check runs and no money moves. Every quickstart and every plugin test uses one.

stablecoin or credit card budget does not refuse it, but no plugin test runs on one. In those modes the core requires signed hops by default (CORE_OWN_HOPS), and a child slice opened without its delegator's signature is refused hop_unsigned. Pass the plugin's hops option (a LayerHops from the agents layer: the delegator's key and each payee's own signed offer) so it signs every hop it opens. n8n and Dify have no such option; see their pages.

CLI, Gemini CLI) opens Control Mode budgets and cannot sign hops, so a core that requires signed hops (the default in every money mode) refuses its streams. It is Control Mode only.

operator allows it, and real-money settlement is not released.

Python plugins

FrameworkPackageFramework pinREADME (in the repository)Test target
OpenAI Agents SDKdynamoprotocol-openai-agents 0.6.0openai-agents 0.23.1packages/plugin-openai-agents/README.mdmake test-py-agents
LangChain, LangGraph, Deep Agentsdynamoprotocol-langchain 0.3.0langchain 1.4.3, langgraph 1.2.14, deepagents 0.7.23packages/plugin-langchain/README.mdmake test-plugin-langchain
LlamaIndex agentsdynamoprotocol-llamaindex 0.1.0 (scoped credentials)llama-index-core 0.14.25packages/plugin-llamaindex/README.mdmake test-plugin-llamaindex
CrewAI (Linux; Docker on Intel macOS)dynamoprotocol-crewai 0.3.0crewai 1.15.23packages/plugin-crewai/README.mdmake test-plugin-crewai
Google ADKdynamoprotocol-adk 0.3.0google-adk 2.11.0packages/plugin-adk/README.mdmake test-plugin-adk
Claude Agent SDKdynamoprotocol-claude-agent-sdk 0.3.0claude-agent-sdk 0.2.163packages/plugin-claude-agent-sdk/README.mdmake test-plugin-claude-agent-sdk
Microsoft Agent Frameworkdynamoprotocol-msaf 0.2.0agent-framework-core 1.20.0packages/plugin-msaf/README.mdmake test-plugin-msaf
Pydantic AIdynamoprotocol-pydantic-ai 0.2.0pydantic-ai-slim 2.54.0packages/plugin-pydantic-ai/README.mdmake test-plugin-pydantic-ai
Strands Agentsdynamoprotocol-strands 0.2.0strands-agents 1.57.2packages/plugin-strands/README.mdmake test-plugin-strands
NVIDIA NeMo Agent Toolkitdynamoprotocol-nemo 0.2.0nvidia-nat-core 1.9.0packages/plugin-nemo/README.mdmake test-plugin-nemo

TypeScript plugins

FrameworkPackageFramework pinREADME (in the repository)Test target
OpenAI Agents JS@dynamoprotocol/openai-agents 0.2.0@openai/agents 0.19.0packages/plugin-openai-agents-js/README.mdmake test-plugin-openai-agents-js
Vercel AI SDK@dynamoprotocol/ai-sdk 0.2.0ai 7.0.133packages/plugin-ai-sdk/README.mdmake test-plugin-ai-sdk
Mastra@dynamoprotocol/mastra 0.2.0@mastra/core 1.74.0packages/plugin-mastra/README.mdmake test-plugin-mastra
LangGraph.js@dynamoprotocol/langgraph 0.2.0@langchain/langgraph 1.4.21packages/plugin-langgraph-js/README.mdmake test-plugin-langgraph-js
Claude Agent SDK (TypeScript)@dynamoprotocol/claude-agent-sdk 0.3.0@anthropic-ai/claude-agent-sdk 0.3.293packages/plugin-claude-agent-sdk-ts/README.mdmake test-plugin-claude-agent-sdk-ts

Workflow platforms

PlatformPackageREADME (in the repository)
n8n@dynamoprotocol/n8n-nodes-dynamopackages/n8n-nodes-dynamo/README.md
Difythe dynamo Dify tool pluginpackages/plugin-dify/README.md

For a gateway in front of any OpenAI-compatible endpoint instead, see LiteLLM and the guard.

What next

these plugins hire each other across owners under one bounded budget.

organisation or team may do.

is accepted.

The tested versions and the record of each pin decision are in docs/integrations/matrix.md.