Join waitlist

Loopmoney

Charge per call, token, or megabyte.
Settle in USDC — without a thirty-cent swipe.

Private waitlist · prepaid · 1.2% take

Join Waitlist

Built for

  • APIs
  • AI models
  • Data
  • Agents
  • IoT
  • Web3

The problem

Digital services are still sold with the wrong unit economics.

01

Subscription fatigue

Developers pay monthly even when usage is occasional, while new customers hesitate to try tools with a high minimum spend.

02

Traditional rails fail at micropayments

Card and bank fees erase margin on small transactions, making high-frequency, low-value charging impractical.

03

Agents need programmable spend

Autonomous systems need granular, automated payments and budget controls that subscription-first billing was never built for.

Solutions

Built around how you actually ship software.

Choose a seat. Loopmoney meters usage, settles in stablecoins, and keeps spend under control for both sides of the transaction.

Charge per call, token, or megabyte

Add the SDK, publish a price, and expose the endpoint. Loopmoney tracks usage, invoices or prepaid balances, and shows revenue by customer without a billing rewrite.

See marketplace discovery for listing and low-commitment trials.

  • Configurable units: per call, per 1,000 tokens, per MB, per second
  • Adjust pricing from live demand instead of annual contracts

Features

A stablecoin rail designed around real software usage.

Metering, USDC settlement, and spend caps in one rail. Open a card for the details.

Usage metering

SDKs capture calls, compute time, tokens, or data volume with configurable billing units.

Send events from the edge of your service. Loopmoney aggregates per customer and per product, then feeds the billing engine. You keep the API; we keep the meter honest.

Micropayment processing

Stablecoin rails for high-frequency, low-value charges that cards cannot price.

Prepaid balances cut credit risk. Hybrid invoicing covers enterprise accounts. Settlement stays small enough that a $0.004 model call still has a business.

Live dashboards

Providers see revenue. Consumers see spend. Both sides get budget controls.

Usage, ARPU, and customer mix on one side. Service-level spend and remaining cap on the other. Analytics APIs exist for teams that already have a warehouse.

Marketplace discovery

A curated directory where buyers try APIs with pay-per-use, and providers can promote placement later.

Loopmoney’s marketplace is a curated directory of APIs, models, and data services. Buyers can trial tools with low-commitment pay-per-use pricing instead of a sales call. Providers list privately or publicly; promoted placement and enterprise invoicing are paid upgrades after the on-ramp.

Pricing playground

See what a micropayment actually costs.

Cards take $0.30 plus 2.9% on every swipe. Loopmoney takes 1.2% of gross. Move the sliders and switch units — this is a working calculator.

Billing unit

Each billed unit is a separate charge on card rails.

Gross usage

$48.00

Card rails (2.9% + $0.30 / charge)

$3,601.39

12,000 swipes × $0.30. Not viable — fees exceed gross.

Loopmoney take (1.2%)

$0.58

Provider nets $47.42

How a payment loops

Four steps from an API hit to settlement.

Select a node. This is the path every call, token, or byte follows.

01 · SDK event

A usage signal leaves your service

The Loopmoney SDK records the call, token count, or bytes at the edge and forwards a signed event. Your API stays yours; the meter is additive.

Dashboards

Same meter. Two consoles.

Play an example week of usage, then watch an agent spend a hard cap. This is the product surface, not a customer case study.

Example week

$18,420

Gross volume · 2.4M metered units

Top route: /v1/complete · 61% of volume

Take captured at 1.2%: $221

Revenue follows usage as it lands. There is no monthly plan on this screen.

Learning · SDK Coming soon

Meter a call in a few lines, then settle it.

This sample is a preview. Full docs ship with the first SDK drop. Providers wrap an endpoint; consumers mint a key, set a budget, and pay as the work runs.

loopmoney.js Preview 
import { Loopmoney } from "@loopmoney/sdk";

const loop = new Loopmoney({ apiKey: process.env.LOOP_KEY });

app.post("/v1/complete", async (req, res) => {
  const result = await model.complete(req.body);
  await loop.meter({
    customer: req.headers["x-loop-customer"],
    unit: "tokens",
    quantity: result.usage.total_tokens,
  });
  res.json(result);
});

Architecture

One loop: meter, price, settle.

You keep the API. Loopmoney keeps the meter, the 1.2% take, and the USDC payout.

01

Metering engine

Receives SDK events, aggregates usage per customer and service, and normalizes pricing inputs.

02

Billing and payment engine

Calculates charges by unit and triggers stablecoin micropayments through smart contracts and payment rails.

03

Dashboards and APIs

Expose analytics, budget controls, invoicing views, and integration points for providers and consumers.

Pricing

What you pay: 1.2% of settled volume.

Take rate

1.2% on gross usage that actually settles. Built for charges that can be fractions of a cent.

Prepaid USDC

Consumers and agents top up a balance. Providers get paid as usage lands — no monthly minimum to start.

Later, if you need it

Enterprise invoicing, promoted marketplace placement, and a white-label rail for platforms that want this billed under their name.

Now → next

Private waitlist, then a small partner SDK.

Now

  • Waitlist open for API, model, and data providers.
  • Metering and prepaid USDC settlement on one chain.
  • Provider and consumer consoles in private preview.

Next

  • Design-partner SDK in a small set of languages.
  • Curated marketplace for low-commitment trials.
  • Agent keys with hard spend caps.

After that

  • More chains and settlement rails.
  • Enterprise invoicing for teams that cannot prepaid-only.
  • Richer analytics for usage, churn, and ARPU.

Private waitlist

Request a seat before the first partner SDK.

We're taking a small set of API, model, and data providers. Enter a work email. You'll get a confirmation on this page — seats open in batches.