Partner integration guide

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.

Dynamo Protocol splits one budget into capped, revocable streams of spending and settles them with signed vouchers. A budget is funded in one of three ways: Control Mode (no money moves, every check still runs), stablecoin escrow contracts, or a credit card authorization. Partners plug in at the edges: they fund a budget, verify who an agent is, move money in and out, or carry Dynamo's caps into their own framework, gateway or platform.

No partner integration is live today. Every adapter described in this guide runs against a local mock, a contract on a local test chain, or a simulator. Dynamo makes no promise about real money: real-money settlement is not released. Live credit card mode is refused in code; stablecoin money mode is gated by the operator's configuration and a Safe multisig check. A live key for Stripe, a card program, a KYA provider or Circle ramps refuses to start the core. The adopted rails take no partner key.

Status labels

LabelMeaning
LiveUsable today in Control Mode or on a local or test chain
PreviewBuilt, behind a switch that is off by default
Release-gatedNeeds real money, live credit card keys or operator-mode ramps; not released

Partner types

Partner typePageWhat runs today
Stablecoin issuers and payment railsRailsLive on local chains and mocks
Card programsCard programsPreview on mocks; live credit card keys Release-gated
Agent verification (KYA) and identity providersIdentityIdentity proofs Live; KYA Preview on a mock
On-ramps and off-rampsRampsPreview on a mock; operator mode Release-gated
Agent framework maintainersFrameworksLive in Control Mode
Gateway vendorsGatewaysLive with mock upstreams
Platform and marketplace hostsPlatformsLive on mock hosts; nothing submitted

What every partner page covers

Each page names:

  1. the interface a partner implements or calls;
  2. the mocks and shared test vectors it runs against;
  3. the test suites (make targets) that must pass;
  4. what runs on mocks today and what would need a partner sandbox or

production access;

  1. the switches involved, if any, and their defaults;
  2. the certification steps: the technical checks a partner must show green

(suites, vectors and named refusals). These are engineering checks only.

Ground rules for every integration

any attesting service sign with their own keys. The core pins each partner's signer address and never holds a partner's private signing key. It holds a test API key only where a switch needs one (the KYA and card program mocks, operator-mode ramps on Circle's sandbox).

service refuses the action, with a named reason. Nothing is guessed.

runs only Control Mode unless its operator allows a money mode (CORE_ALLOWED_MODES, default none).

core requires every delegation hop to be signed by its own parties by default (CORE_OWN_HOPS).

The test suites run from a clone of the repository; see Add Dynamo to an agent framework for the general setup (Node, pnpm, Python 3.11).