Loomal

Track revenue from your Loomal listings.

Every paid call settles on-chain and carries a signed receipt, so your revenue numbers aren't estimates — they're verifiable. Here's how to read them, reconcile them, and turn them into pricing decisions.

Revenue tracking for an x402-monetized server is unusually honest. There's no 'pending' bucket, no chargeback window rewriting last month, no payment processor reconciliation file: a call either settled in USDC on Base or it didn't, and settled is final, usually within about two seconds of the request.

That changes what tracking means. Instead of auditing whether the numbers are real, you spend your time on what they imply — which listings earn, which tools drive volume, and whether your price is leaving money on the table.

Know where the numbers come from

Each paid call produces two artifacts: a USDC settlement on Base to your payout wallet, and an Ed25519-signed receipt tied to the call. The console's revenue view is built from this settled activity — which is why its totals are facts rather than projections.

This also means revenue recognition is trivial. A settled call is earned, immediately and irreversibly; there is no deferred-revenue bookkeeping for refund windows because the rails don't have refund windows.

Watch calls and settled revenue as separate signals

Track both numbers per listing, because they diverge in informative ways. Settled revenue is price times paid calls — so flat revenue on rising call volume means agents are concentrating on your cheapest usage patterns, while falling volume after a price change tells you where buyers' budget caps sit.

Per-listing granularity matters most when you run several servers. One listing quietly producing 90% of settled USDC is an argument for investing there — better tool descriptions, more capacity — rather than spreading effort evenly.

Reconcile against the chain

Your payout wallet's transaction history on a Base explorer is an independent record of every settlement, which makes reconciliation a comparison rather than an investigation: console totals for a period should match the wallet's incoming USDC for the same period. The 5% fee on settled transactions is currently waived, so today those two numbers should align without an adjustment.

Do this monthly even though it almost always matches. The point isn't distrust of the console — it's that a mismatch is a high-signal alarm (a misconfigured payout address, an accounting bug on your side) that's far cheaper to catch in month one than at tax time.

Turn trends into pricing moves

Revenue history is your pricing lab notebook. The repricing loop: note the date you change the price, give it one to two weeks, then compare settled revenue and call volume against the equivalent prior window. Revenue up on modestly lower volume means the raise worked; volume cratering means you crossed the budget caps common among your callers.

Look for time-of-week structure too. Agent workloads are often scheduled — pipelines that run nightly or weekly produce regular spikes, and a recurring spike disappearing usually means one significant integrator left. That's worth noticing within days, not at the end of the quarter.

Keep receipts for the long game

Signed receipts are more than per-call proof — accumulated, they're an auditable usage history nobody can dispute. That history prices your enterprise conversations ('here's our settled volume, cryptographically'), backs up whatever you report for taxes, and settles any disagreement about what was served and paid.

Practically: export or archive your settled activity on a schedule, keyed by listing and date. The chain keeps the settlements forever, but having your own organized copy turns any future question into a lookup.

FAQ

How soon after a call does revenue show up?

Settlement on Base completes in about two seconds, and your handler only runs after payment clears — so by the time your server has responded, the USDC is already yours. There's no payout schedule or holding period; settlement goes to your wallet directly.

Can a payment be reversed after I've served the call?

No. USDC settlement on Base is final, and x402 has no chargeback mechanism. The number you see settled is the number you keep, which is why settled revenue can be treated as earned immediately rather than provisionally.

How do I verify Loomal's numbers independently?

Check your payout wallet on any Base block explorer: every settlement is an on-chain USDC transfer you can count and sum without trusting anyone's dashboard. Per-call receipts are Ed25519-signed, so individual calls are independently provable too.

What does Loomal deduct from my revenue?

The fee is 5% of settled transactions, and it's currently waived — so at present, settled per-call revenue arrives undiminished. There are no listing fees or monthly charges on top; the fee model is purely a share of revenue that actually settles.

Watch the meter run.

Calls, settled USDC, and receipts — per listing, in one place.

Go to the Loomal console