01
Earn
Your service takes payment per request
Customers and agents pay through x402 and Circle Nanopayments. Every payment settles onchain, so revenue is observable without you reporting it.
Reading settled payments…
Every figure on this page is the book itself.
Read from the protocol, not a marketing deck. Losses, defaults and utilization are published on the same surface as the numbers that flatter us.
Total value locked
—
Utilization
—
Realized losses
—
Outstanding credit
—
Active borrowers
—
Default rate
—
Revenue routed 30d
—
Principal repaid
—
Repaid from revenue
—
Earn, score, borrow, repay — then borrow more.
A credit line is not granted once. Each completed repayment is evidence the loop works, and evidence is what lifts the cap on the next assessment.
02
Score
Revenue becomes an underwriting input
Rivora reads settled payments, uptime, refund rate and customer concentration. The constraint that binds your limit is shown to you, not hidden behind a score.
Constraint ladder · reassessed every 14 days
03
Borrow
Draw against the line in USDC
Funds land in the operating wallet you registered and spend inside a policy you set — category limits, per-payment caps, an approval threshold.
Limit 2,530.00 USDC · finality 0.6s
04
Repay
Settlement services the debt first
A fixed share of every settled batch repays the loan at the router. Interest is applied before principal, and paying early costs nothing.
20% of settled revenue · ~90.00 USDC/day
04 → 02One completed cycle raised this borrower 1,690.00 → 2,530.00 USDC
Three things stand between a loan and a promise.
Unsecured lending to an anonymous machine only works if repayment is enforced by plumbing rather than intent. Each of these is checked continuously, and each is visible to the borrower on their own screens.
01
Revenue cannot route around the protocol
The payTo your endpoint advertises is bound onchain to a Revenue Router you deploy. A probe compares the two continuously. If the advertised address drifts, new draws stop and the repayment share escalates.
—
02
The split happens before you are paid
Under custody Model A the router divides each batch at the moment it settles: 20% to repayment, 2% to the loss reserve, the remainder to your operating wallet. Repayment is not a transfer you have to remember.
20 / 2 / 78 enforced at the router
03
Losses reach the protocol before lenders
A first-loss tranche absorbs defaults ahead of liquidity providers. Defaults are recorded permanently in a public registry — a record may be cured, but it is never deleted.
—
The other side of the book
Lend to revenue, not to a balance sheet.
Supply USDC to the credit vault and hold a claim on a book that amortizes continuously — roughly 2.2% of outstanding principal returns every day out of routed revenue, rather than at a maturity date.
Displayed APY
—
Organic yield
—
Mean payback
—
Coverage multiple
—
⚠ Arc Testnet. Test assets only, no real value. Credit scores are experimental. Rivora is not a licensed lender in any jurisdiction.