Saved toolsSubmit a tool
FOXAI SEARCH

Search FoxAI

News stories 126

funding

Startup Founders Are Using AI To File Patents. Here’s Where DIY Becomes A Liability.

AI can help startups reduce patent preparation costs, but DIY applications may overlook critical issues. In this guest commentary, attorneys Michael Drapkin and Nathan Mutter of AI-Native law firm Landfall IP, argue that combining AI with legal expertise can produce more efficient, commercially valuable patent protection that withstands investor scrutiny and is harder for competitors to circumvent.

Crunchbase News
rag-methods

FinEvolveKG: Controlled and Attributable Prompt Evolution for Financial Knowledge Graph Construction

arXiv:2611.08643v1 Announce Type: new Abstract: Financial institutions construct knowledge graphs (KGs) from shared SEC 10-Ks to serve risk analysis, portfolio management, and investment research, whose analytical needs differ. Extraction must adapt without fragmenting shared grounding, typing, and temporal rules. Hand-authored persona prompts and fine-tuning add cost. Weight-free prompt optimization offers an alternative, but unconstrained evolution of a monolithic prompt can rewrite shared rules alongside persona guidance, obscuring changes and complicating review. We introduce FinEvolveKG, a KG-construction harness separating reusable general and persona-policy blocks and mechanically confining GEPA, a reflective prompt optimizer, to the designated block. During persona adaptation, the approved general block remains byte-stable and every optimizer edit is localized to a separately versioned persona policy. A dual objective balances generic temporal-KG quality with persona-relevant facts, motifs, and multi-hop connectivity. We evaluate five mutation scopes on ticker-disjoint 10-K splits, with three seeds for the persona-conditioned arms (v3-v5) across three personas. On the three-seed mean, the complete two-stage block-constrained workflow (v4) improves over the frozen prompt baseline (v1) by 19.4-30.9% and over the tested unconstrained full-prompt workflow (v5) by 2.2-6.4%, leading v5 on both objective components and winning all nine paired-seed comparisons with the lowest seed variance in every persona. Without further optimization, v4 also exceeds v5 across all evaluated out-of-distribution (OOD) shifts. An SME audit supports using the generated triplets as ground truth; a blinded two-SME audit favors v4 over v5 in 70.1% of contrast-enriched judgments. These results show that mechanically attributable evolution can coexist with strong empirical performance, without attributing the gains causally to the boundary.

arXiv cs.CL
startup-projects

Show HN: Control Layer Demo for AI Coding Agents

Letting coding agents (such as Claude Code) work autonomously on repos on a daily-basis, brings a high level of uncertainty. For those who won't let the agent decide alone whether it can create/modify or delete any folder on their repos; I wanted to be able to trace actions performed and being able to let the agent continue his work autonomously, or ask him to request a human approval according to some criteria defined. After investigations, the cleanest way to do it was according to me to develop a deterministic control layer between the LLM and the work of the agent that would track and catch potential non-respect of pre-defined rules. How? by first setting up approval rules (Pass/requires approval/refused) before the work of the agent, and afterwards controlling cryptographic SHA 256 verifications, etc. This allows to compare the before-after work of the agent. I have put in my public GitHub repo a demo that you can launch easily and observe different scenarios behaviors like applied authorized modification, protected file waiting for Human approval, or outside perimeter authorization modification refused. The demo is offline, does not involve the official runtime, in native node.js and without dependencies. It should still allow you to understand the core principles. I would like to know: how do you implement and handle safety boundaries? Especially if you let agents work on critical data/sensitive codebases? With which guardrails? Comments URL: https://news.ycombinator.com/item?id=50422833 Points: 1 # Comments: 0

Hacker News Show HN
startup-projects

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

Hacker News Show HN