
FLINT · Know Your Agent for the Agentic Economy
Verify AI agent identity and authority through FLINT's reputation network.
@RealADVON · X
The full gallery
Tech stack
60 projects

Verify AI agent identity and authority through FLINT's reputation network.
@RealADVON · X

Upload PDFs and videos to build a visual knowledge map, then query an AI research assistant.
allybahaei · HN
Bring all your sources into a visual space, ask questions with full context, branch LLM conversations, and go deep on YouTube videos / research papers to build your knowledge canvas.

Ask questions about the world and see answers on a map with live geospatial data.
@agenticearth · X

AI platform to ask questions, generate images, and speak hands-free for better decision-making.
@Akinzoooo · X

Verify AI agent decisions locally with transparent reasoning and MCP integration.
brandon_grutkowski · Product Hunt
Aurora Glass-box Quantitative AI for Humans and Agents

A dashboard for traders to replay trades, analyze behavior patterns, and optimize their trading system.
@Crypto77qi · X
最近一直在@dappOS_com上体验 @xBubble_ai 的 Coding,这两天我给自己做了一个 AI Trading Replay(AI 交易复盘助手)。 👉 做交易时间越久,我越觉得,真正拉开差距的,并不是找到更多交易机会,而是不断减少重复犯同样的错误。 现在币圈已经有很多成熟的交易工具,行情、链上数据、资金流向、技术指标几乎都能找到对应的平台。但这些工具更多是在告诉我们市场发生了什么,却很少帮助我们分析,为什么面对同样的市场,每个人最终的交易结果却完全不同。 有时候并不是没有机会,而是因为犹豫错过了;有时候方向看对了,却因为害怕提前离场;还有时候连续几次亏损之后,下一笔交易开始变得犹豫,最终又错过真正的行情。 这些问题,并不是增加一个指标或者再多看一份数据就能解决。 所以我没有继续做一个新的行情工具,而是直接用 xBubble Coding 做了一个 AI 交易复盘助手。 它不会预测市场,也不会告诉我什么时候买卖,而是把每天的市场变化、自己的交易记录和决策过程整理下来,通过 AI 自动分析哪些判断是正确的,哪些错误一直在重复发生,并生成每天、每周的交易复盘,让整个交易过程形成一套可以不断优化的闭环。 整个开发过程也比我想象中轻松很多。 没有写代码,没有配置服务器,也没有部署环境,只需要把自己的需求描述清楚,一个可以直接访问的网站很快就搭建完成了。从原来的一个想法,到真正变成可以使用的产品,中间几乎没有任何开发门槛。 我觉得,这也是 xBubble Coding 最有价值的地方。 它并不是让大家重复开发一个市面上已经存在的软件,而是让每个人都能把自己的经验、工作习惯和思考方式快速变成真正属于自己的工具。 未来真正有价值的,或许不是拥有越来越多标准化的软件,而是每个人都能根据自己的需求,打造一个最懂自己的 AI 工作伙伴。

Real email inbox, login automation, OTP handling, and credential vault API for AI agents.
u/kumard3 · Reddit
shipped delivered/bounced/replied webhooks, and deliberately left out open-pixel tracking an agent that sends mail needs to know what happened to it. i had delivery and bounce events sitting in the database the whole time, they just never got delivered anywhere useful, so an agent sending mail had no way to react to a bounce or know if anyone replied. shipped webhooks for the real lifecycle: delivered, bounced, complained, replied. an email.replied event fires specifically when an inbound

Practice system design by submitting architectures and experiencing AI-triggered production incidents.
u/No-Preference-846 · Reddit
I built an AI-augmented system design practice tool that triggers a live production incident when you submit your design - not just a critique Every system design prep resource I used was static — read a diagram, read the tradeoffs, move to the next one. Nothing ever pushed back on what I actually built. So I built ChaosBench . You design a system on a canvas — drag components, wire them up — and when you submit it, an LLM (Gemini) finds the actual weak point in your specific design and

Interactive map showing how exposed different jobs are to AI across 17 countries.
uxff · V2EX
做了一个 AI 职业风险地图,直观看看各个国家各个行业的工作受到 AI 冲击的程度 前段时间自己频繁搜索 AI 会如何影响我从事的职业,我周边的人从事的职业,然后又开始搜索哪些职业很难被 ai 代替。搜到的信息很零散,几乎没有数据完整、可视化好的网站。 所以我做了一个可视化网站: ## AI Job Risk Map https://aijobriskmap.com 网站使用 Treemap 展示不同职业的 AI 风险。每个方块代表一个职业: - 方块大小表示职业规模 - 颜色表示 AI 风险等级 - 可以按国家查看职业分布 - 可以比较不同职业和职业类别 - 支持查看具体职业的风险数据 目前主要覆盖美国、英国、加拿大、澳大利亚、新西兰及欧洲、亚洲的多个国家。风险评分关注的是职业中的任务有多少可能被 AI 自动化或显著改变,并不等同于预测某个职业会彻底消失。 这个项目仍在完善中,尤其希望听听大家对下面几个问题的意见: - 风险地图是否容易理解? - 你更关心“职业被替代”,还是“职业会如何被 AI 改变”? - 除了风险、薪资和就业规模,

Build and visualize AI agents executing live on an interactive dashboard.
@Aurelsuuu · X
this is my product, come take a look:

Paste URLs to get AI transcriptions and summaries organized on an infinite canvas.
@trytacit · X
Building TACIT to stop stop saving and start applying

Share context across AI agents so they remember your codebase and task history.
@dorikuio · X
AI agents have amnesia — Claude Code figures out the codebase, an hour later Codex starts from zero. So I built a shared memory + task board for every MCP agent — Claude Code, Codex, Cursor, Gemini CLI: Is this just my problem? Help me find out.