@LadeLade007 · X

The API-first licensing platform for developers who need subscription, perpetual, or usage-based models without building infrastructure from scratch.

@yrecurringhq · X

yRecurring is an AI-Native subscription and billing platform. 14 days free trial - no credit card required.

@FrankFika · X

Still using a chat app to send files to yourself? I built USend: no sign-in, no app, no permanent share link. An 8-digit code moves a file or text between devices. Browser-side encryption. Auto-delete after receipt or expiry. Try it: #VibeCoding #OpenSource

13639366668 · HN

Pay-per-call MCP server with 47 AI endpoints, micropayments via x402

nparashar150 · HN

Over the weekends, I've been revamping an old side project of mine: https://quik.run/?ref=yc It started as a simple platform for writing and sharing code snippets. Over time, it evolved into a way to run snippets instantly with support for imports and packages, without worrying about setup, deployment, or infrastructure. Think of it as a lightweight AWS Lambda for quick experiments. One thing I've realized is that even though AI has made a lot of older developer tools and ideas feel less relevan

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

u/Zyron_X · Reddit

I built a service for people to use Codex API without 5-hour limit disruption I built a small service for people who use the OpenAI Codex API regularly and want more predictable usage without the 5-hour or weekly limits. It currently provides: Frontier OpenAI models (GPT 5.6 family included) Managed API key Monthly usage budgets depending to plan No 5-hour limit No weekly limit Under the hood, it is built on top of an open-source project and proxies requests to

4seasons · V2EX

devfun.org - 开发者（网络）工具集合 ## 访问地址 https://devfun.org ## 主要功能 - 本机 IPv4/IPv6 网络检查及 IP 信息查询 - 站点可访问性检查（支持全球区域） - 代理检查及代理全球出口检查 - 各类编解码、格式测试、文本格式化、校验密钥生成、文本处理、转换工具 欢迎大家使用，提供建设性的建议和意见！

@bingobray · X

我做了一个类似的工具: 除了支持公众号，还支持word和pdf😁

@Dckrig · X

Because once the requests start flying, so do the costs. Build smarter. Spend smarter. #AI #VibeCoding #BuildInPublic #Startups #Credlier

u/Sapos_re · Reddit

I kept losing track of my roadmap while vibe coding, so I built a visual progress tracker When I started building apps with AI, writing the code no longer felt like the hardest part. The hardest part was understanding where I actually was in the project. After a few sessions, my roadmap would become increasingly difficult to follow. The agent would complete tasks, change files, and suggest new steps, but I would gradually lose sight of the bigger picture: What has actually been comple

@afhammk · X

You do know that it's just a claude wrapper . right..? And I haven't even heard anyone talking about in the vibe coding community. It's a worse platform than lovable, replit etc. I still don't get why is somehow an argument for icp.