Clerk did for auth what @ai-billing does for AI billing.
Wrap your model, define a destination, and every request is automatically metered and charged. No billing infra to build.
Adding usage-based billing to your AI app shouldn't take a weekend.
@ai-billing wraps the Vercel AI SDK - one middleware, 5 lines of code.
npm install @ai-billing/core and you're done.
https://t.co/RsAGPWFCCm
Good job @stripe with @𝘀𝘁𝗿𝗶𝗽𝗲/𝗮𝗶-𝘀𝗱𝗸 package. Users of Lago, Openmeter and Polar - we got you too with @𝗮𝗶-𝗯𝗶𝗹𝗹𝗶𝗻𝗴/𝗹𝗮𝗴𝗼 @𝗮𝗶-𝗯𝗶𝗹𝗹𝗶𝗻𝗴/𝗼𝗽𝗲𝗻𝗺𝗲𝘁𝗲𝗿 and @𝗮𝗶-𝗯𝗶𝗹𝗹𝗶𝗻𝗴/𝗹𝗮𝗴𝗼.
1/2 Using LLM providers directly saves budgets.
You're paying 1.6x more for input tokens and 2.4x more for output tokens using Grok 4.20 Multi-Agent at @OpenRouter vs going directly to @xai
And if you cross the 200k context window? That premium jumps to over 3x and 4x.
Team Narev shipped beautiful billing components to narevai/ai-billing.
Adding usage-based billing to a Next.js app is now as simple as adding two lines <CreditTopUpPolar/> <CreditUsagePolar/>
Pure spring cleaning in our open source project. We've overhauled the dependency stack to the latest lines (node v24, hello).
Hats off to the @Mend_io team for their Github bot. So easy to get everything updated.
Did @DeepInfra just silently add Xiaomi MiMo models?
Pulled their models endpoint and spotted both V2.5 and V2.5-Pro sitting there.
Same pricing as Xiaomi's <=256K tier.
Looks like @DeepInfra are matching Xiaomi’s base tier direct pricing exactly:
- XiaomiMiMo/MiMo-V2.5-Pro: $1 In / $3 Out / $0.20 Cache Read
- XiaomiMiMo/MiMo-V2.5: $0.40 In / $2 Out / $0.08 Cache Read