NAll news

All news

Wednesday71 items

Tuesday63 items

  2. rohan_paulProduct release
    AI score58

    English translation is being prepared.

    Quoted postDigitalOcean · @digitalocean

    Catch it at the first user, not the four-hundredth. A new user’s bank link fails, the agent says “try again later,” and nothing shows up in the logs. Watch a team find the bug and fix it before anyone else hits it, with Agent Learning Services and Agent Data Services, launching today.

    #Product updates#Agents#English text is being prepared.

  3. shao_mengProduct release
    AI score65

    English translation is being prepared.

    Quoted postSpaceX Super Intelligence · @SpaceXSI

    We've unified plans across Grok, Cursor, and X Premium. Introducing The X Subscription. https://t.co/SvkrVvBa0p

    #Industry news#OpenAI#Anthropic

  4. shao_mengProduct release
    AI score58

    English translation is being prepared.

    Quoted postIshaan · @ishaan_jaff

    We're open sourcing agentchat, it's a unified SDK that allows you to connect your agent to Slack, Teams, iMessage, email, and WhatsApp in 2 lines of code and works with any agent SDK We noticed we kept on rebuilding the stack to connect our agents to different channels and ended up building the same shared layer. That's where agentchat came in. This allows you as a developer to focus on your core agent's brain and let the SDK manage your connections with different channels.

    #English text is being prepared.#Agents#English text is being prepared.

  5. shao_mengProduct release
    AI score51

    English translation is being prepared.

    Quoted postSumanth · @Sumanth_077

    Jev as a judge for LLM evals! JevEval uses Jev as the judge for custom LLM evals instead of relying on another generative LLM for every evaluation. The idea is pretty simple. You define the exact decisions you want the evaluator to make, Jev evaluates each one and returns probabilities, and DeepEval uses those results to calculate the final score. For example, with an AI agent you can evaluate the trace itself, checking whether the agent selected the right tools, followed the expected sequence of actions, and actually completed the task. Jev handles those semantic judgments, while the scoring logic stays outside the model. That is the main difference from a normal LLM-as-a-judge setup. With a generative judge, the model often has to interpret the rubric, reason about the response, and generate the evaluation itself. With JevEval, you define the decision structure upfront. You can also assign different weights to different checks or use `strict_mode` when every requirement needs to pass. So if one part of the agent workflow matters more than another, you can reflect that directly in the scoring logic instead of leaving the entire evaluation to the judge model. Key capabilities: - Evaluate agent outputs and traces with Jev - Define custom checks as bounded decisions - Use yes/no, score, and closed-choice questions - Weight different checks or require all of them to pass - Evaluate both single-turn outputs and multi-turn conversations This is where Jev makes a lot of sense for evals. If you already know what needs to be checked, you can define those decisions upfront, let Jev handle the semantic judgment, and keep the final scoring deterministic. I’ve shared the DeepEval post in the comments.

    #Evaluations / benchmarks#Agents#Product updates

  7. openrouterFirst-partyProduct release
    AI score51

    English translation is being prepared.

    Quoted postNeal Patel · @neal_k_patel

    You already gave the LLM the answer. So why is it writing it out from scratch? Introducing a new AI model architecture: Constrained Decoding Models (CDMs) LLMs were built to write. Most production workloads just need an answer: fast, consistent, and affordable. CDMs are purpose-built for 1 task each. They read your input once and skip the token-by-token generative loop that makes LLMs slow and expensive. Not just a decision model, but a family of 3 CDMs live today: • Classify: define your labels and get back a calibrated probability + reason for each. Used for routing, tagging, and intent detection. • Extract: describe the entities in natural language and get back well-formed JSON with confidence scores + citations. Used for web scraping, document processing, and PII redaction. • Summarize: pass in long text, images, or PDFs and get back a consistent summary under 1,000 tokens. Used for context compaction, metadata generation, and transcript digests. Built for production: • 1M tokens of multimodal (text + image) input, 31x larger than Jev • 77.2% on DecisionBench vs Jev's 72% • 200x faster, 467x cheaper than frontier LLM APIs • $0.05/M input tokens. Output is free (yes, even for summarize) Live on your favorite platforms today: @OpenRouter @vercel_dev @LiteLLM @LangChain @TrustedRouter @itsArthurAI @useRouterPlus Get 50M input tokens for free (for the first 50 hours) at link below 👀

    #Product updates#English text is being prepared.#OpenAI

  8. rohan_paulProduct release
    AI score51

    English translation is being prepared.

    Quoted postAlexander Whedon · @alex_whedon

    Introducing SubQ Snap, the first long-context decision model for real enterprise work. Snap is the only decision model or LLM where compute per token stays constant as context grows. • 384K tokens of multimodal context, 12x larger than Jev. • 61.7 on Decision Index v0.2.1 vs Jev’s 57.9, outperforming on 13 of 16 enterprise benchmarks. •Processes 100K tokens and returns a decision in under one second. •$0.05/MM input tokens. Output is free. Available today to anyone. The first 10,000 sign-ups get 100M free input tokens. We’ll likely hit capacity fast and will add users as we add compute. Compute offers welcome 🙂. Latency will be variable as we tune the platform to this new model and category of users. Model speeds are 80ms for minimal context, 250ms for 32k, 660ms for 100k, and 2.5 seconds for 384k. Visit: https://t.co/Nc76iJF2a8

    #Model releases#Reasoning#Multimodal