Urgent.News

What's breaking now, across thousands of outlets.

AI

Anthropic Reportedly Posted Quarterly Revenue Growth of 50% and Was Cash-Flow Positive. Here's Why It Might Not Be Enough to Impress Investors Before the Company's Massive IPO

Key PointsSome reports say Anthropic generated $16.8 billion in revenue for the quarter ending Sept. 30.

Anthropic reportedly posted a 50% increase in quarterly revenue to $16.8 billion, as well as being cash flow positive and profitable on an adjusted basis. While this performance may seem impressive for investors before the company's anticipated $2 trillion IPO, it's not without its concerns. The growth rate has slowed from the previous quarter's 140% growth, and the revenue figures fall short of market expectations.

Analysts have questioned whether the company's expectations for revenue are realistic, with some suggesting it needs to reach $105 billion by the end of 2026. Despite Anthropic's positive cash flow and adjusted profit, investors are scrutinizing the company's valuation and focusing on the funding and cost of capital required to maintain such growth.

The company has already delayed its registration twice, and the AI safety concerns surrounding the industry further complicate the situation. Despite Anthropic's impressive growth numbers, the valuation debate remains the main focus for investors as they weigh the risks and uncertainties surrounding the company's massive IPO.

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

This story

This is one outlet's version. Read the fullest account.

Read the original at nasdaq.com →

More in AI

DeepSeek swapped its Flash model overnight. I pulled the new config and did the cache math.

On October 17, DeepSeek replaced the model behind its deepseek-flash API endpoint. Same name, same price, no changelog entry you had to go read — if your agent called deepseek-flash on Friday and…

  • DeepSeek replaced its Flash model with DeepSeek-V4.1-Flash-1017 on October 17
  • KV cache compression varies from 688 to 5.4 bytes per token depending on context length
  • API pricing shows cached input tokens are 50 times cheaper than uncached

Debugging LLM JSON Output: From Frustration to Function Calling

Alright, fellow builders. Let me tell you about a particular rabbit hole I found myself tumbling down for a good couple of weeks.

  • Developer struggled with unpredictable JSON output from language models.
  • Language models like GPT-3.5-turbo and GPT-4-turbo generated faulty JSON for complex prompts.
  • Switching to function calling eliminated raw JSON and syntax errors.

More from Sunday 18 October →