Payments at the tempo of machines.

Sub-cent, per-request, signed a thousand times a second — settled once on the XRP Ledger. Built for agents that pay for what they consume, in the grain they consume it.

Movement I — The Stream

Value, sustained.

A payment shouldn’t be an event. Tremolo holds it as a note: thousands of signed, sub-cent claims flowing between machines, opened once and closed once. Nothing in between touches the ledger.

  1. Open.

    A payment channel is opened on-ledger, once. A bounded amount, a single payee, an expiry, and a close condition — all set at the moment you open it, all enforced by consensus.

  2. Sustain.

    Claims are signed off-ledger at the tempo of the work: per token, per second, per request. Each claim supersedes the last, so a dropped message costs nothing. Nothing waits for a block. Nothing pays a fee.

  3. Settle.

    The final claim is redeemed on-ledger. One transaction closes what a million notes performed. Finality in about four seconds, with no reorgs to wait out.

Movement II — The Performers

Machines don’t invoice each other.

An agent that calls a model, rents a GPU-second, buys a row of data, or hands work to another agent has to pay in the same grain it consumes. Invoices settle in thirty days. Card rails floor out near thirty cents. Neither can price a forty-millisecond inference. A stream can.

Humans never wanted to watch money tick — every metered consumer product died on that. Machines don’t watch. They meter. Tremolo is the payment rail for the payer that finally doesn’t mind.

  • Per-inference metering

    Meter what actually ran — tokens, milliseconds, rows — and let the claim value move with the meter, continuously. The bill and the work are the same event.

  • Agent-to-agent settlement

    An agent delegates a task and pays as results arrive, not when an invoice clears. No accounts receivable between things that don't have accounting departments.

  • Bounded delegation

    Hand an agent a channel key, not your wallet. It can sign claims to one payee, up to one cap, until one expiry — and nothing else. A fully compromised agent loses, at most, the remainder of one channel. That's the whole blast radius.

  • Human sets the tempo, once.

    Budget, payee, limit, expiry — set at open, revocable at will. The person sees a flat number. The stream runs underneath. That's the arrangement: humans keep the flat rate; machines stream beneath it.

// illustrative — the client API is not public yet
const channel = await tremolo.open({
  to: gpuProvider,
  cap: xrp(50),                 // ledger-enforced ceiling
});

for await (const ms of inference.meter()) {
  const claim = channel.sign({ amount: drops(ms * 12) });
  await gpuProvider.deliver(claim);          // off-ledger, ~0 latency
  // channel.total → 3 184 220 drops (3.184220 XRP), running
}

await channel.close();                       // on-ledger, once
Illustrative code: open a channel, sign one claim per metered unit of work, close once.

Movement III — The Instrument

The primitive was already there.

Streaming isn’t bolted onto this ledger. Payment channels are a native transaction type on the XRP Ledger — live since 2017. The locked amount, the claim verification, and the settlement rules are enforced by consensus, not by a contract someone deployed and hopes was audited. Tremolo plays the instrument as built.

  • Native, not contracted.

    No bytecode between your funds and the rules. The validators are the rules.

  • A channel is already a mandate.

    Bounded amount. Fixed payee. Dedicated signing key. Expiry. Owner revocation with a settle delay. Tremolo composes these into delegated spending authority a human can grant in one signature and take back in one more.

  • Non-custodial by construction.

    Tremolo never holds funds and never holds keys. The payer's channel key stays with the payer; the provider's keys stay with the provider. We construct, verify, and meter. We never touch.

  • Honest about the edges.

    Channels settle in XRP; fiat-denominated pricing is pinned per quote window. Rate and price ceilings are enforced by the provider; caps, payee, expiry, and revocation are enforced by the ledger. We say which is which, everywhere.

  • 3–5s

    ledger close

  • 1,000,000

    drops per XRP — sub-cent granularity is native

  • Native

    payment channels. No bridge, no L2, no wrapped assets

  • <$0.01

    typical transaction cost

Coda

One signature to open. One to close. Everything between is music.

Request access.

Tremolo is in private access for agent frameworks and metered-resource providers building on the XRP Ledger. Tell us what you’d stream.

No newsletter. One email, when there’s something to use.