For people who fund a budget

This page is for you if an app or service asks you to fund a budget: an amount you set aside that the service can draw on as it works for you, and never beyond. It explains how you fund it, what you can see, what you can stop, and what stays in your own hands.

Each feature carries one of three labels:

chain.

this release: a deployment refuses to start with live credit card keys.

Nothing on this page is a promise about real money.

Funding a budget

With a credit card, on the service's top-up page (Live with test cards)

The service sends you a link to a short page. It shows the most the budget can spend, who it pays, and when the offer ends, with one Authorize button.

uses is captured; the rest of the hold is released when the budget closes.

the service can send you a new link.

authorizes with a test card token.

come from that page, is recorded as your consent to fund the budget.

Release-gated.

Paying a person or an agent from the console (Live)

If you use the console yourself, the People and payments view lets you fund a budget and pay a person or an automated agent from it.

your wallet for one signature and sends only that signature; your key never leaves the wallet.

This works only while you are signed in to the console, never with an API key.

paid once.

Other ways (Preview)

Funding through a stablecoin on-ramp exists behind a switch that is off by default; where an operator turns it on, it uses your own provider account and delivers only to the budget's funder. Operator-run ramps are Release-gated.

What you can see

The service can give you a link to your portal (Live). It shows, for each budget linked to you:

revoked;

its state.

The service can also send you a read-only link to one budget, or show a balance and receipts on its own pages. These links expire, and the service can revoke them at any time.

What you can stop

From the portal you can, on self-hosted and hosted deployments alike:

until the service resumes it. You cannot resume it yourself.

already delivered is signed and settled first, so what the service proved it did stays payable, and nothing more. If a settlement fails, the revoke still goes ahead and its signed record lists the work that was not settled.

Every freeze and revoke is written as a signed record. The portal only acts on your own budgets: an allowance that belongs to someone else looks exactly like one that does not exist.

One limit:

until that claim is settled, even though the portal already shows it as revoked.

Receipts and proof

can be checked offline, with no connection to the service, with dynamo verify <evidence-file.json> --signer 0x…. Ask the service for the signer address it publishes and always give it: without it the check trusts the signer named inside the file.

chain.

What offline verification covers. The verifier checks every signature and digest in the file. From evidence/1.5.0 on it binds and checks each stream's sessionKeyAddress against the vouchers. Pair the file with on-chain settlement (or the engine-signed payment records) to complete a money proof. It is weakest on Control Mode and the credit card rail, where there is no chain to check.

If something goes wrong

Disputes (Live) are opened by the budget's owner, so ask the service to open one for you. They are decided on objective facts only: a breach of terms the service agreed to, reported by a measurement signer from the operator's catalogue that the budget's owner opted into (Preview: it needs a deployment with a terms catalogue); a task step that was not delivered; or a payment that does not match its signed receipt. Where the facts allow, the refund goes back to the payer first, from funds still held. Once a payment is final it is not reversed through Dynamo; the evidence file is what you can take to the service or to someone you both trust. See Recourse.

A refund is possible only where the service you use offered refund terms and you accepted them before using it; AI inference itself (text, image, video, compute time) carries no refunds, and Dynamo never decides a refund itself. Unspent budget returned when a budget closes is not a refund: it was never spent.

Your keys and your wallet

for you.

from that wallet, and on stablecoin budgets anything returned to you goes to that wallet's address. Keep a backup the way your wallet recommends.

(for the service's developers)