DYNAMO PROTOCOL
One budget. Many agents.
Payment streamed by the second.
Across the universe.
Build AI services with programmable payments designed for faster settlement, efficient transactions, and commerce across borders. From inference and data to agents that work with other agents.
Start in Control Mode with no money moving. Escrow is on Base Sepolia testnet; production payment rails require per-instance review. Explore availability →
Example assumes an identity-priced settlement asset and a 1% fee. A signed voucher is a claim; payout timing and finality depend on the rail.
Your next customer could be an agent.
Your next service could power a whole workflow.
01 · AI DEVELOPERS
Sell inference, tools, APIs, compute, and data to an economy of human and autonomous customers.
Settle metered work as it runs. When funds arrive depends on the payment rail.
A 1% default token-rail fee can lower costs for small payments. Network costs are additional.
Accept supported tokens across borders, where your deployment and local requirements allow.
Put access, metering, and token payments inside your app’s logic, with capped agent allowances.
Price by call, second, or sub-cent unit. Choose settlement intervals that fit your costs.
Connect agents, models, and data providers. Track their work and payments under one budget.
Fee terms are deployment-specific. The published escrow contract permits fee changes within a 10% ceiling; the rate at settlement applies. A protocol fee does not include every service provided by a card processor or marketplace. Inspect the contract source →
SHOWCASE · INTEGRATE WITH DYNAMO
10 lines to your first metered, paid call. DreamCade and DreamReel show the integration pattern: connect your app, meter delivery, and settle as work runs.
An AI pipeline designs, builds, and tests the game. Dynamo connects that work to metering and payment.
An AI pipeline creates short episodes. Dynamo connects shot delivery to metering and payment.
Both apps use Base Sepolia testnet assets today. Production activation requires review; payout timing follows the rail. Refunds, retries, and provider charges need app-specific handling.
FUNDING MODES & AVAILABILITY
Build in Control Mode, simulate payments on testnet, then enable production payments after review. Your own compute and service costs still apply.
Connect your app and test usage metering and budget limits for free. No funds move.
Run escrow transactions on Base Sepolia with testnet tokens. Test the payment flow without risking real funds.
Let customers pay by card without a wallet or blockchain onboarding. Availability and payout terms require processor approval.
Review the key and custody model for your deployment. A hosted operator may control the budget-owner key. Contract restrictions do not establish self-custody for every user, and public source code is not an independent security audit.
START BUILDING
Start with a dedicated instance and a small, measurable workflow. Validate control behavior before adding real funds.
Tell us what you’re building. The team provisions your instance and confirms access.
Use the SDK or MCP, LiteLLM, Kong, and APISIX integrations. Set units, prices, and limits in Control Mode.
Test escrow on Base Sepolia. Enable production payments after security and payment-provider reviews.
02 · AI USERS
FOR AI SERVICE USERS & AGENT OPERATORS
Give agents room to work, with explicit authority, clear limits, and records you can inspect.
Share one budget across agents and providers. Caps cover routed work; external charges and network costs are separate.
Issue scoped, capped credentials. Revoke access under your deployment’s enforcement rules.
See usage and signed claims by service. Match them to settlement and agreed terms.
Test caps, concurrent requests, revocation, and recovery in Control Mode. No money moves.
Dynamo Guard connects supported service requests to the enforcement core. Correct routing, shared-state coordination, and key handling are essential to the spending boundary. Explore Guard →
MULTIPARTY ORCHESTRATED PAYMENTS
A single outcome can depend on several providers. Dynamo brings delegated budgets, metering, and settlement claims into one workflow.
One research task. Separate allowances for inference, data, and a specialist agent.
Meter model usage and record claims for eligible work.
Account for access to the data needed for the task.
Delegate a bounded task with its own usage record.
Link usage and signed claims to the service branch that requested them.
Set each service’s allowance and see usage across the workflow.
Match records to settlement. Coordinate enforcement across concurrent requests.
Use durations, counts, or recorded acceptance to connect service activity to payment terms.
Set measurable quality conditions and trusted measurement sources. A signature identifies the source; it does not prove quality.
Cumulative vouchers track usage; settlement pays the accepted increment. Handle retries and external charges separately.
Refunds follow the payment rail, app rules, and available funds. Revocation does not reverse settled payments.
03 · THE INTERPLANETARY AI ECONOMIC AND FINANCIAL LAYER
Space-based AI infrastructure is an active research direction: Google’s Project Suncatcher explores satellite constellations equipped with TPUs and optical links for machine learning compute. Explore the research →
THE GRAND VISION
An economy where AI agents earn, spend, and collaborate across borders and across space.
As AI takes on more work, it needs ways to exchange value, coordinate services, and account for resources. Dynamo’s ambition is to become an economic and finance layer for that activity: connecting intelligence, compute, data, and the businesses built around them.
That ambition reaches toward space-based inference, data centers, observation data, relay bandwidth, and power availability. Today’s budgeting, metering, and payment capabilities are building blocks within that larger vision.
Independent services buy inputs, deliver outputs, and exchange value.
Meter service-specific units with clear measurement sources and payment terms.
Verify signed records offline with trusted keys. Fresh balances and revocations still need communication.
Extend local authority, timing, reconciliation, and settlement for delayed or disconnected links.
Interplanetary operation is a long-term ambition, not a deployed capability. A future token or dedicated ledger would require separate technical, economic, and operational justification.
BUILD THE ECONOMY OF INTELLIGENCE
Dynamo — The Interplanetary AI Economic and Financial Layer.
Start with what you can build today. Help shape what comes next.