Urgent.News

What's breaking now, across thousands of outlets.

AI

Grok Bot Now Offers ‘Free’ Claude Opus 5.5 and Midjourney

Elon Musk says Grok Bot will no longer stick to SpaceXAI’s own models alone. In a post on X on … Read More The post Grok Bot Now Offers ‘Free’ Claude Opus 5.5 and Midjourney appeared first on ProPakistani .

Grok Bot Now Offers ‘Free’ Claude Opus 5.5 and Midjourney

Elon Musk announced on X on October 7, 2026 that Grok Bot, the assistant developed by SpaceXAI, will no longer be limited to using only SpaceXAI's own models. The AI assistant will now select the best backend model for each specific task, including leading models such as Anthropic's Claude Opus 5.5, Midjourney, and Suno. This means that Grok Bot users will have the ability to access these high-quality AI models at no additional cost.

However, users will still need to pay for Grok Bot itself. The decision on which model to use will be made automatically based on the specific request, with heavy reasoning and long-form tasks directed towards Claude Opus 5.5, image jobs to Midjourney, and music and audio to Suno. The "free" access offered by this system is simply a way to reach these top-tier models without having to pay separate fees for each API.

While the pricing and privacy rules for using these third-party models are not yet specified by Musk, the move signals a trend among major platforms of keeping the user interface while outsourcing certain model work to more specialized providers. This approach allows platforms to offer premium features without charging users for each individual API call.

Written by urgent.news from ProPakistani's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at propakistani.pk →

More in AI

5 Mistakes That Make LLM Streaming Break on a Flaky Network

Your chat UI looks fine on the office Wi-Fi. Then someone joins from a train, the SSE connection drops mid-sentence, and either the answer restarts from scratch or the model keeps burning tokens while…

  • Tying generation to the HTTP request causes wasted computation when the connection is lost.
  • Lack of sequence IDs prevents clients from reconnecting and resuming the generation process.
  • Using "error" as an event name can confuse the default EventSource error handler.

More from Saturday 10 October →