Billing for RPC, APIs & compute.
Meter usage, enforce quotas and settle every cycle in stablecoins — with webhooks wired straight into your provisioning, so paid means on and past-due means throttled.
Made for metered services
If it has a quota, a key or a node, Subsie can bill it on schedule.
Paid means on. Automatically.
The settle → webhook → provision loop closes in seconds, in both directions — past-due throttles, recovery restores.
Charge settles
The cycle charge is pulled within the customer's cap and confirmed on-chain in seconds.
Webhook fires
payment.settled hits your control plane with a signed, typed payload.
Key provisioned
Your backend raises the quota, mints the key or unsuspends the node — no human in the loop.
Micro-invoices that stay profitable.
On Base, Arbitrum or Optimism a settlement costs cents, so a $9 starter plan or a $3.20 overage line doesn't drown in processing fees.
- Charges routed to the chain you choose, L2-optimized
- Subsie fee ~0.3–0.5% per settled payment — no monthly minimum
- Overage billed on the same allowance, never a second approval
Illustrative at ~0.45% — network fee billed at cost
Infra teams ask
Can we drive billing entirely from the API?
Yes — plans, subscriptions, usage records and charges are all REST resources. The dashboard is optional.
How fast can we suspend on non-payment?
payment.past_due fires the moment the final retry fails; most teams throttle immediately and revoke after a grace window.
Does overage need a new approval from the customer?
No — overage settles within the same capped allowance. If an invoice would exceed the cap, the charge waits and the customer is asked to raise it.
Wire billing into the control plane.
Model quotas and overage in the console, then script it all over REST. Live settlement arrives as the platform matures.