Your AI product
Short answers cost almost nothing and long ones cost more. The meter tracks your GPU bill on its own.
priced per answer
Pay per use infrastructure
Cladior signs your visitors in and charges them for the data they use. You set the price, and your code stays the same.
Short answers cost almost nothing and long ones cost more. The meter tracks your GPU bill on its own.
priced per answerTen thousand calls or ten calls. Nobody has to choose a tier before they've tried it.
priced per callReaders pay for the essay they opened, not for twelve months of essays they'll never get to.
priced per articleMortgage maths, tax estimates, unit converters. They're useful for a minute and worth a fraction of a cent.
priced per useResize, upscale, remove a background. Big files bill bigger, without a pricing page doing any arguing.
priced per fileSell a clean export to the one person who needs it today, then to the next one tomorrow.
priced per downloadWhatever you build next, it can charge for itself from the first request.
Meter itCladior sits in front of whatever already serves the site. Nothing is redeployed and nothing is rewritten.
Skip the auth sprint and the billing sprint. If it runs on a server, it can charge.
Heavy users pay more and light users pay less. Your margin doesn't depend on guessing who's who.
Payments happen between the visitor and Cladior. Your servers never handle a card number.
Buy credit once and spend it across every app that runs on Cladior, without a new signup each time.
An app can't quietly raise your rate. A new price means asking you again.
Disconnect an app and it can't charge you again. Unused credit stays yours for the next app you try.
No. Your server keeps receiving ordinary HTTP requests and answers them as it always has. The only change is a DNS record.
Only if your origin is left open. Lock it so it only accepts traffic from Cladior, using client certificates on nginx, Deployment Protection on Vercel or a site password on Netlify.
The request body plus the response body, measured per request and rounded up to the kilobyte. Headers aren't counted, and any path you mark as free isn't billed at all.
New users see the new rate. Anyone who already connected keeps the rate they agreed to, so nobody's price changes without them being asked.
Earnings appear the moment a request is billed. You can withdraw from $5 once two-factor authentication is on, to a bank account in your name. Payouts arrive within 5 business days.
No. Cladior never shares email addresses with apps. You get a stable user ID if you ask for it, and if you need to contact someone you can ask them directly.
Need a quick summary? Ask an AI about us.
app.post('/webhooks/stripe', async (req, res) => { const sig = req.headers['stripe-signature'] const event = stripe.webhooks.constructEvent(raw, sig, SECRET) if (event.type === 'invoice.payment_failed') await suspend(sub) if (event.type === 'customer.subscription.deleted') await revoke(sub) return res.json({ received: true })}) app.use(session({ store: new RedisStore(redis), secret: SESSION_KEY }))passport.use(new LocalStrategy(async (email, password, done) => { const user = await db.users.findUnique({ where: { email } }) if (!user || !(await argon2.verify(user.hash, password))) return done(null, false)})) return renderChapter(book, chapterId) const sent = Number(res.getHeader('content-length') ?? 0)await db.usage.increment({ userId, bytes: sent, at: startOfHour() })const invoice = await stripe.invoices.create({ customer, auto_advance: true })if (invoice.status === 'uncollectible') await suspend(userId) Click in and change a line.
Written yourself, auth and billing is a file of payment webhooks, sessions, password hashing and usage metering, and it is yours to maintain. With Cladior your visitor sees one screen showing the exact rate per kilobyte, agrees to it before anything is charged, and there is no equivalent file to write.
Register your app, add one record, and start earning from the first request.