osquarski OpenAI example Since OpenAI does not include cost, I use a custom pricing map to return it
osquarski @ai-billing also sends usage events to Billing Providers Here is an infographic how: And a codesnippet showing how to do it for: Stripe Polar Lago OpenMeter
osquarski Installation Full-stack @ai-billing examples Name Demo Link Repo Deploy Chatbot (OpenRouter + Polar) View Demo GitHub Chatbot (OpenAI + Polar) View Demo GitHub Chatbot (Stripe) View Demo GitHub
BestCodes @r2hu1 This is a fork of OpenCode right? Or maybe based on OpenTUI. I'm curious what advantage it had over OpenCode, why should I use it instead? It looks really cool! 😃
r2hu1 it isn't a fork, its based on open tui and it do have few advantages but not built to compete opencode i built it to understand behind the scenes of coding agents
BestCodes That's awesome! Great job @r2hu1 🙂
Mike Tickstem Update: Tickstem now includes status pages that auto-generate from your uptime monitors and heartbeat checks --- no manual "we're investigating" posts needed. The page reflects your actual monitor state in real time. If your monitors are green, the page is green. If an endpoint goes down, the page updates automatically. You get a public URL at tickstem.dev/status/your-slug --- shareable with users, no separate service needed. Works well alongside Vercel deployments: monitor your API routes, set up a heartbeat on your background jobs, and your status page stays current without any manual update
Mike Tickstem Update: Tickstem now has an MCP server --- if you use Claude Code or Cursor alongside your Vercel projects, your AI assistant can register cron jobs, create uptime monitors, and set up heartbeat checks directly from the editor. Remote option (no install): connect via mcp.tickstem.dev/mcp --- works with any MCP-compatible client. Local binary option: go install github.com/tickstem/mcp/cmd/tsk-mcp@latest Same API key you're already using. Useful when you're scaffolding a new Vercel project and want the agent to wire up monitoring as part of the build.
Amy Egan Can you tell us more about how you built this? Is it open source?
Rish Built it with Next.js on the frontend, with a backend that provisions ephemeral machines to run the code changes. It uses the Anthropic API for the model layer and integrates directly with GitHub and Vercel's APIs for deployments and PRs. The Telegram bot handles the conversation layer. One thing I spent a lot of time on was dynamically right-sizing the compute and selecting the right model based on repo context and change complexity, so that simple fixes don't spin up more than they need to. Not currently open source.
Joecelaster @abhivarde , This is cool. I'd love to contribute. Is this open source ?
Abhivarde thanks! not open source currently, maybe later 🙂 curious though, what would you want to contribute or improve!?
Abhivarde update on snipply shipped offline support. here's how it works: → supabase anonymous auth gives every visitor a silent identity the moment they land. no form ever appears → supabase rls lets anyone read components but only you can edit your own → every save hits supabase and indexeddb at the same time → go offline, saves still work locally. come back online, header dot turns green and you're synced → shared links load from local cache if you've opened them before. a small "cached" badge tells you full local-first with supabase doing the hard parts live: snipply.abhivarde.in
Ryu This is a strong project idea. The "100 small tools" format makes it easy to follow, and keeping each tool free/open-source gives people a reason to come back as the collection grows. The current set already covers useful developer utilities: URL metadata, redirects, rate limiting, AI summaries, and file conversion. Those are exactly the kind of small tools people often need once and do not want to sign up for. One thing that could make the project even more useful is adding a simple "request a tool" or voting section, so people can suggest which utility should be built next. That would also m
Webrenew Love the idea - but what if it was agnostic to runtime/host?
