u/ASDKING100 · Reddit

Launched an AI API router tonight, and found a bug hours in that would've taken real payments without ever upgrading the account Built LLMLite over the past few weeks — it classifies each prompt and routes it to the cheapest model that can actually handle it, instead of hitting GPT-4o for everything. Free tier, no card needed to try it. Tonight, right as I was about to launch, ran a real transaction to test the payment flow end to end. Paddle processed it, webhook fired, signature verified

@Scyloq · X

Currently building SentrAI. The merge-time control plane for AI-assisted software development. Enforce policy, audit every AI-generated change. Just finished an interactive demo and would love your honest feedback. Built with @Lovable

@SublimeDr85198 · X

@eldrex_bula · X

lemma1729 · HN

Hi HN, This is ProofTree, and in TLDR: it is a platform where you can chat with an AI to do math, the way you already do, with context-awareness and knows how you personally do math, connected to the fora of other live human mathematicians. So, when you are talking to an AI about a proof at 3 am, and you need a human expert looking at it, or a discussion around it, like you do on StackExchange, this is it! You need an approved email account to use it, so please write here if you would live to try it out.

@akadhanu · X

an ai sprint retrospectives for it teams (

@Lathithaa_Mdayi · X

Aarav03790 · HN

I made AI agent that deploys your thing on diff plats automaticaly

@liquidated0x · X

building an AI coding agent that ships full projects from a prompt — if you're if you're curious

tahazsh · HN

Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t

@Nogui_1 · X

A digital wellness ecosystem to make peace with our digital selves.