Skip to content
AI NEWS JOURNAL
AI, IN PERSPECTIVE

Search AI news

Search headlines, summaries and articles to connect the dots.

Newest first

Show HN: I hand-read 248 shops' return policies because no dataset existed

I missed a return window last month because the policy page and the order confirmation said different things. Turns out return windows don't exist as data anywhere. So I've been reading them by hand. 248 shops, 8 countries. Each record stores the sentence the number came from, the URL and the date I read it. 331 more are in the list unread and marked as such. Free, no signup. MCP server at pricemend.com/mcp if you want an agent to use it. An early version of my parser read "within one year of the event date" off Target's gift registry page and recorded a 365 day return window. That's why there's a quote on every record now. Is the confidence field useful, or over-engineered? Comments URL: https://news.ycombinator.com/item?id=50489829 Points: 1 # Comments: 0

Show HN: Open-source customer-facing agents

Hi, Dmitri from Radioso here, an open-source platform to design AI agents for customers and visitors in any channel, in the style of Fin/Ada/Decagon. The repo is https://github.com/radioso-ai/radioso and our website is https://radioso.aiToday, your choices are:1. Buy a very expensive service for your vertical (usually starting with $$ five figures monthly) 2. Get a cheap off-the-shelf chatbot that mostly answers FAQs 3. Build your own, and then also build the inbox, human handoff, audit trail and integrations around itAt Radioso we wanted an open-source option that combines the best of all 3. You can integrate it with your own software via API/SDK or your CRM, or run it standalone, either self-hosted or in our cloud.The engine runs multi-step interactions and takes actions: calling your APIs, updating records, booking things. Maybe you’ve tried Parlant; Radioso is the alternative “with batteries included”: RAG, audit trail, customer service inbox, and integrations like Slack and email.Under the hood it’s plain TypeScript + PostgreSQL, works with OpenAI/Anthropic/other models, and is licensed under Apache 2.0 which includes all features (The only thing we keep under EE license is the multi-tenant layer we use to run our own cloud).We have existing customers running it for technical Q&A, course booking, online product recommendations and goods returns, among others, some reaching 92% of conversations automated. We’re currently working on voice support so we can offer a call center.Our ambition is to be “the WordPress of customer-facing AI” :), where people can contribute their favorite plugins and benefit from the ecosystem.Longer term, we think browsing the web will mostly mean talking to your own agent, and when you need a service or a purchase, your agent will talk to the vendor’s agent to get things done. For this, Radioso already publishes an A2A Agent Card and we’re working on the rest. Your Radioso services are also callable over MCP, for customers who already use it.Thanks for your attention. We’d especially love to hear which integrations you’d want, whether you’d self-host it, and what’s stopped you from deploying a customer-facing AI agent so far. Tell us what you think. Comments URL: https://news.ycombinator.com/item?id=50423820 Points: 1 # Comments: 0