Loading video...

Video Failed to Load

Go Home

Developers have been using the Decisions API to: • Route requests to the right model, tool, or agent. • Turn scaled inputs into useful labels, rankings, and scores. • Analyze images, compare visual content, or identify key video frames. • Choose buttons, navigate forms, or determine actions from screenshots....

160,290 views • 13 days ago •via X (Twitter)

9 Comments

OpenAI Developers's profile picture
OpenAI Developers13 days ago

Powered by GPT-6 Luna, it accepts text and image inputs and supports 3 kinds of outputs: Predicates: Estimate the probability that a statement is true. Choices: Select from predefined options, with confidence scores. Scores: Evaluate an input against a numeric range.

OpenAI Developers's profile picture
OpenAI Developers13 days ago

Let your app choose the right model, tool, or action in near real-time with Decisions API, now available to all developers in public beta. The Decisions API makes decisions up to 10x faster than GPT-6 Luna through the Responses API.

OpenAI Developers's profile picture
OpenAI Developers13 days ago

You can now try the Decisions API in public beta:

Patrick Schaub's profile picture
Patrick Schaub13 days ago

"Route requests to the right model, tool, or agent." @theo it's time to challenge this again?

Adam's profile picture
Adam13 days ago

Please don't force me to use this. This will never work well.

Ishu Agrawal's profile picture
Ishu Agrawal13 days ago

How would Luna have any idea of the “right model” to route to

Jason Rai's profile picture
Jason Rai13 days ago

Video input support please

John Herzog's profile picture
John Herzog13 days ago

flagging risky tool calls before they run could save agent builders a lot of cleanup

Hidden Hall's profile picture
Hidden Hall13 days ago

Will this be available in aws?

Related Videos

10 agent evals every AI engineer should know 1) golden set a frozen set of cases you run after every prompt model or tool change use it as your baseline to see whether the system improved or quietly broke OpenAI Evals helps you build repeatable benchmark sets and compare model changes → 2) llm as judge a second model scores open ended answers against a written rubric use it when there is no exact output to compare against OpenEvals provides ready made evaluators for LLM applications → 3) rubric scoring score correctness tone safety and cost separately one quality number hides the problem DeepEval helps you create custom metrics and score every dimension independently → 4) trajectory eval grade the path the agent took not only the final answer AgentEvals checks agent actions decisions and tool calls across the full trajectory → 5) tool unit tests test every tool with fixed inputs and outputs no model in the loop MCP Inspector helps you inspect and test MCP servers tools and responses separately → 6) regression suite replay previous runs against every new prompt model or toolset then compare the results Promptfoo helps you run repeatable eval suites catch regressions and add checks to CI → 7) a b in prod split real traffic between two versions and compare actual outcomes GrowthBook provides feature flags controlled experiments and product analytics → 8) human review sample real runs and let a person grade them honestly use it to calibrate your automated judge Argilla helps teams collect human feedback review outputs and build better datasets → 9) shadow run let the candidate run on real traffic while its output is shown to nobody use it before a risky rollout Langfuse helps you trace production runs compare candidates and monitor eval results → 10) red team attack the system before somebody else does jailbreaks prompt injection data leaks and tool abuse Garak scans LLM systems for vulnerabilities and unsafe behavior → offline evals tell you it works online evals tell you it still works you probably do not need all ten today start with the two that would have caught your last outage bookmark this

elune

155,026 views • 2 months ago

HERMES AGENT WITHOUT TOOLS IS A CHATBOT. WITH THEM IT BUILDS 3D TOWERS IN BLENDER, CHECKS STOCK PRICES, AND DRIVES VS CODE. tonbi JUST DROPPED THE FULL GUIDE. module 6 of his 10-part Hermes masterclass. best breakdown of the tool layer anyone has published. what you need to know: TOOLS vs SKILLS vs MCP skills = instructions (markdown, loaded into context) tools = callable functions (Python, agent emits call, Hermes executes) MCP = adapters to external systems (Blender, Stripe, Linear, Notion) every tool has three parts: → the function (does the real work) → the schema (what the model sees to decide when to call it) → the registry (makes the tool exist in the agent) the model never runs the function directly. it emits a structured request (tool name + JSON args). Hermes executes and returns the result. if the tool fails, the error goes back as JSON. the agent recovers instead of crashing. TOOL SETS CONTROL THE SURFACE hermes chat --tool-sets web # only web tools loaded. no files, no terminal. hermes chat --tool-sets safe # read-only: web search, vision, image gen. # no file writes. no terminal. no code execution. mid-session: /tools enable video /tools disable terminal or toggle in the dashboard: hermes dashboard → Skills → Tool Sets MCP SERVERS two transport types: STDIO (local subprocess) or HTTP (remote endpoint). add a server: hermes mcp # or ask: "add the MCP server for Blender" filter tools with include/exclude per server. keep only what you trust. security: → OAuth 2.1 PKCE (no long-lived tokens in config) → package scanning via api.osv. dev before launch → all MCP calls go through approval gates HERMES AS MCP SERVER hermes mcp serve exposes 10 tools via FastMCP. connect VS Code Copilot or Cursor to your running Hermes instance. BUILD YOUR OWN TOOL He built a stock price tool live: → Python function calling Finnhub API → schema with name, description, parameters → registered in tool_sets.py → agent calls it automatically when relevant any repeating API call in your workflow can become a native tool. full Hermes architecture deep-dive in the article 👇

YanXbt

32,680 views • 4 months ago

Karpathy’s Agentic Engineering finally has proper DevTools! When an agent stops working, the model is only one possible cause. The problem could be a failed tool, a lost connection, an interface update that never appeared, or something earlier in the conversation. CopilotKit🪁 has rebuilt its open-source Inspector around this problem. It sits inside the application and watches the full interaction between the user, the interface, and the agent. When something fails, the Inspector button turns red, names the failure, and opens the spot where it happened. But even a much harder problem is reproducing that failure. This is because agents do not always follow the same path twice. Running the same prompt again may trigger another tool, produce another response, or start with a different application state. Inspector handles this through saved Threads and an isolated Agent Playground. A developer can open the conversation where the problem occurred, choose "Try from here," and copy everything up to that point into the Playground. The original conversation remains unchanged while another response or tool path is tested. Threads can open inside the live application, while assistant messages can jump back to their matching context in Inspector. Everything runs underneath AG-UI, the protocol that carries messages, tool activity, state changes, and other events between the agent and the interface. Those interactions can also feed CopilotKit Intelligence so that when the same issue or useful behavior appears repeatedly, it can become an evidence-backed Insight and a proposed SKILL(.)md file. Developers can review, edit, and approve the improvement before the agent inherits it. The tool also helps developers find a problem, recreate its surrounding context, test another path, and turn repeated lessons into agent improvements. It is open source and included with CopilotKit development builds. Intelligence setup starts with one prompt. Here are the docs: I am testing this extensively and will cover this in more detail soon with a hands-on demo.

Akshay 🚀

12,206 views • 1 month ago