Anthropic OpenAI Rivalry Shifts From Better Models to Better Data
- Ethan Carter

- 2 days ago
- 12 min read
Anthropic and OpenAI face a new competitive test after reports linked Anthropic to a takeover of Decart, an AI infrastructure and world-model startup. The talks remain unconfirmed, yet they sharpen a larger conflict. Frontier labs can keep producing better models, but deploying those systems efficiently has become a different problem.
The reported transaction would give Anthropic technology designed to make training and inference workloads use computing hardware more efficiently. Inference is the process of running a trained model to answer requests. It consumes more resources as usage grows, even when the expensive initial training run has finished.
Glasswing Ventures founder Rudina Seseri framed this tension during a Bloomberg interview about the reported talks. She argued that the success of companies such as Anthropic and OpenAI also exposes their limitation: they are not efficient enough. Her broader point was not that model research has stopped mattering. It was that better data, infrastructure, and workload optimization now determine whether model intelligence becomes an economical product.
That distinction changes how investors, developers, and enterprise buyers should interpret the Anthropic OpenAI contest. The visible race concerns benchmark scores, coding ability, agents, and reasoning. The less visible race concerns how much useful work each company can extract from every chip, dataset, and customer interaction.
The Reported Decart Talks Put Efficiency at the Center
The Decart report matters because Anthropic appears interested in owning more of the system beneath Claude, not merely improving the model itself.
According to the original acquisition report, Anthropic has discussed acquiring Decart. Neither company had publicly confirmed a completed agreement when the report appeared. The negotiations should therefore be treated as an active report, not a finished transaction.
Decart describes its work through two connected areas. The first involves real-time world models, which learn patterns representing environments and their changes. The second involves software that optimizes how AI training and inference run across computing hardware.
Its infrastructure stack is the more strategically relevant part of the reported deal. Decart says that stack helps reasoning models and agents run faster while using available processors more effectively. The company also builds real-time video and physical-world systems on top of that foundation.
That combination offers Anthropic several possible advantages. It could improve the efficiency of Claude workloads, reduce dependence on default software layers, and speed experiments across different processors. It could also place Anthropic closer to hardware-level decisions that model developers usually leave to chipmakers and cloud providers.
Decart says its AI infrastructure supports both optimized workloads and real-time generative systems. Those claims have not received complete independent validation across Anthropic-scale deployments. Still, the product direction explains why a frontier model company would investigate the business.
World models attract attention because they extend generative AI beyond text. A world model tries to represent how an environment behaves, allowing a system to predict or generate its next state. Potential applications include robotics, interactive media, simulation, and video generation.
However, Anthropic does not need to become a video company for Decart to matter. The same engineering used to generate changing environments in real time can demand tight control over memory, latency, and processor utilization. Those capabilities also matter when millions of users call language models.
The reported talks therefore trigger the article’s central tension. Anthropic built its position through frontier model research and Claude’s adoption. That success creates heavier infrastructure demands, making efficiency a condition for continued growth rather than a secondary engineering goal.
An independent deal analysis reached a similar conclusion. It suggested that Decart could help Anthropic control compute costs and move closer to the technical territory occupied by major chip suppliers.
The outcome remains uncertain. Anthropic might complete a deal, pursue a partnership, or walk away. Yet the reported interest already reveals what the company considers strategically scarce: infrastructure knowledge that turns expensive intelligence into usable capacity.
Anthropic OpenAI Competition Has Moved Below the Model
Anthropic OpenAI competition now extends from model quality into data pipelines, inference economics, hardware utilization, and product feedback loops.
Frontier AI companies once communicated progress mainly through larger training runs and better benchmark results. Those indicators still matter. They no longer describe the whole competitive system.
A model can lead an evaluation while remaining difficult to deploy profitably. It can also perform well on public tests but struggle with noisy enterprise information, long workflows, or unfamiliar user requests. Better model weights do not automatically resolve those problems.
The pressure comes from usage. A training run happens during model development, but inference happens whenever a customer submits a prompt or an agent takes an action. More adoption therefore produces more recurring demand for processors, memory, networking, and electricity.
Reasoning models intensify that challenge because they can generate many intermediate tokens before returning a final answer. Agentic products add tool calls, retries, document retrieval, and verification steps. A single visible request can initiate a much larger hidden workload.
That makes unit economics central to the Anthropic OpenAI rivalry. Unit economics measure the revenue and cost associated with serving a unit of demand. For AI companies, the relevant unit might be a token, completed task, coding session, or customer workflow.
An efficient provider can serve more work with existing capacity. It can also offer faster responses, support longer tasks, or reserve expensive models for requests that need them. These product choices affect user experience as directly as benchmark improvements.
OpenAI has publicly described efficiency as a system-level problem. Its recent infrastructure strategy says economics depend on more than additional data centers or model design. Hardware, utilization, routing, and product decisions also shape the return on computing resources.
Anthropic faces the same equation. Claude’s strength in coding and enterprise workflows can attract demanding users whose sessions involve large repositories, long contexts, and repeated tool calls. Those customers provide valuable demand, but they also create complex infrastructure loads.
This explains Seseri’s observation that success becomes a limitation. A popular model company cannot treat efficiency as a laboratory optimization. It must serve growing demand while maintaining response quality, reliability, safety, and acceptable latency.
The forced response is vertical integration. That phrase describes a company taking control of more layers in its supply chain. In this case, the layers include model research, training data, inference software, cloud capacity, and potentially processor design.
OpenAI has pursued broad infrastructure partnerships and increasingly presents itself as a platform spanning models, products, and computing capacity. Anthropic has deep relationships with large cloud providers while continuing to develop its own model and product layers.
A Decart transaction would not remove Anthropic’s dependence on outside infrastructure. Frontier training and large-scale inference still require extensive facilities, processors, and power. It would instead give Anthropic another way to optimize what happens after it receives that capacity.
That distinction matters for enterprise buyers. They should not assume that the provider with the largest model or newest release will always deliver the best operational result. Reliability, latency, data grounding, and total workflow cost can matter more than a small benchmark lead.
Developers already encounter this tradeoff when choosing models for applications. The strongest model may be unnecessary for classification, extraction, or routine support requests. Routing simple work to smaller systems can improve speed and reduce resource use without damaging results.
The leading labs therefore face pressure from two directions. They must keep advancing frontier capability while matching cheaper systems on practical efficiency. Falling behind on either side can weaken the entire product.
Better Data Can Beat Another Round of Scaling
The central reversal is that more computing power creates diminishing business value when the training and retrieval data provide weak signals.
“Better data” does not simply mean collecting more documents. It means selecting information that teaches useful behavior, covers difficult cases, and reflects the tasks a system will actually perform. It also means removing duplication, errors, spam, and misleading patterns.
Training data shapes a model before deployment. Post-training data then teaches the model how to follow instructions, apply preferences, use tools, and avoid unsafe behavior. Evaluation data helps developers determine whether those interventions work beyond a narrow benchmark.
OpenAI says its foundation models use publicly available information, licensed or partnered material, and information created by users, trainers, and researchers. Its training data summary also identifies synthetic data as part of model development.
Synthetic data is information generated by another model or simulation rather than directly collected from people or the physical world. It can provide targeted examples for rare tasks, safety cases, or structured reasoning. It can also reproduce hidden errors if developers lack strong filters and evaluations.
Anthropic also relies on extensive post-training and safety research. Its competitive challenge is not merely acquiring a larger corpus than OpenAI. The company needs data that improves Claude’s performance on valuable workflows without introducing brittle behavior or excessive serving costs.
That changes the meaning of scale. Traditional scaling laws linked better performance to more data, model parameters, and computing power. The next phase asks whether labs can obtain more learning from each example and more useful work from each generated token.
Data quality becomes especially important when models approach saturation on familiar public benchmarks. Additional examples from the same distribution can produce less improvement. Carefully designed tasks, expert feedback, and adversarial cases can reveal weaknesses that volume alone hides.
Enterprise applications make this issue concrete. A general model may know standard accounting terminology but lack access to a company’s current contracts and internal policies. Connecting that model to trusted, permissioned information often improves answers more than replacing it with a slightly newer model.
Retrieval-augmented generation addresses this gap by placing relevant documents into the model’s context during a request. The model does not need to memorize every changing fact during training. It instead receives selected evidence when producing an answer.
This approach introduces its own data problem. Poor retrieval can surface outdated, duplicated, or irrelevant passages. A capable model may then produce a confident answer from weak evidence.
Organizations therefore need clean information systems alongside capable models. A searchable AI knowledge base can help workers organize source material before an assistant uses it. The model remains important, but information quality sets the ceiling for grounded work.
Better data also includes feedback from real usage. When users reject answers, correct generated code, or abandon an agent midway, those outcomes reveal product weaknesses. Labs can convert that evidence into evaluations and future training examples.
This feedback loop benefits large providers because they serve many interactions. It can also become a limitation. Raw user activity is not automatically high-quality training material, and privacy controls restrict how providers can use it.
The provider must distinguish successful outcomes from superficially plausible ones. A coding agent that produces accepted text may still introduce a hidden defect. A support assistant may satisfy a user while quietly violating policy.
High-quality data therefore requires judgment, labeling, and evaluation infrastructure. It cannot be reduced to harvesting more prompts. The strongest pipeline connects real failures to representative tests, then uses those tests to guide training and product changes.
This mechanism explains why data and efficiency reinforce each other. Better examples can help smaller models handle routine tasks. Better routing can send only difficult requests to expensive frontier systems. Better evaluations can prevent teams from spending compute on changes that improve a headline score without improving customer outcomes.
It also explains why Decart’s infrastructure could complement Anthropic’s model research. Faster experiments let researchers test data mixtures and training interventions sooner. More efficient inference produces more capacity for evaluations, agents, and long-running tasks.
The competitive advantage would not come from data alone. It would come from a closed loop connecting data selection, model behavior, evaluation, workload optimization, and user outcomes. Both Anthropic and OpenAI are working toward versions of that loop.
Cheaper AI Does Not Prove the Data Thesis
Efficiency is improving rapidly, but public evidence cannot yet isolate how much progress comes from better data, smaller models, hardware, software, or lower margins.
The strongest support for an efficiency shift appears in declining inference costs. Stanford’s 2025 AI Index found that the cost of reaching GPT-3.5-level performance on one benchmark fell more than 280-fold between late 2022 and late 2024.
The same AI cost analysis found that much smaller models reached performance thresholds once associated with vastly larger systems. These results show that useful capability can become cheaper and more compact over time.
They do not prove that better training data caused the improvement. New processor generations, quantization, model architecture changes, distillation, competition, and lower provider margins can all reduce prices. Public disclosures rarely reveal the exact contribution of each factor.
Quantization reduces the numerical precision used to store or run a model. Distillation trains a smaller model to reproduce selected behavior from a larger system. Both can lower resource requirements without changing the underlying training corpus.
Benchmarks create another uncertainty. A system can improve because developers trained directly or indirectly on similar examples. It may then struggle when customers present unfamiliar tasks, messy documents, or changing conditions.
This is why claims about superior data need careful treatment. Anthropic and OpenAI disclose categories of training information, but neither publishes a complete recipe for frontier models. Outsiders cannot directly compare dataset quality, filtering, synthetic-data methods, or evaluation coverage.
The Decart report has a similar verification gap. Decart describes software that extracts more performance from computing hardware. Public demonstrations of real-time generated environments show low-latency ambitions, but they do not establish results inside Anthropic’s production stack.
Integration risk would remain even after a completed acquisition. Infrastructure software interacts with hardware drivers, model architectures, cloud schedulers, and reliability systems. An optimization that works for one workload can perform differently at another scale.
World models add strategic ambiguity. They could become important for robotics, simulation, and interactive media. They could also distract Anthropic from Claude’s strongest market if the company treats them as a separate model race.
The more coherent interpretation focuses on infrastructure. Decart’s workload optimization is directly connected to Anthropic’s serving constraints. Its world-model products show what that infrastructure can support, but they should not replace the article’s efficiency thesis.
There is also a competitive response problem. OpenAI, Google, Meta, cloud providers, and chip companies are not standing still. Each can improve compilers, routing, smaller models, custom processors, or data pipelines.
Google has an especially strong position across models, custom chips, cloud infrastructure, search data, and consumer products. OpenAI has large-scale product feedback and extensive infrastructure partnerships. Meta can use open models and its consumer platforms to distribute improvements widely.
Anthropic would still need to demonstrate that deeper infrastructure ownership creates measurable benefits. Relevant indicators include latency, model availability, useful output per unit of compute, and the quality of agents completing long tasks.
Buyers should also resist equating lower model prices with lower workflow costs. An inexpensive model that needs repeated corrections can cost more than a capable model that completes the task once. Human review time belongs in the calculation.
The same caution applies to data. A large private corpus can be valuable, but only when it is current, permitted, searchable, and relevant. More proprietary information is not automatically better information.
Security and governance further complicate the strategy. Training or retrieving sensitive data creates obligations around consent, access control, deletion, and auditability. A high-quality dataset that cannot be used legally or safely has limited operational value.
Synthetic data carries a different risk. Models can amplify their own stylistic habits and mistakes when generated examples dominate a pipeline. Developers need independent evaluations and real-world evidence to detect that feedback loop.
These limitations do not invalidate Seseri’s argument. They refine it. Better data and infrastructure matter because raw scale is insufficient, not because model research or compute has become unnecessary.
The decisive evidence must come from deployed performance. If Anthropic serves more demanding Claude workloads with lower latency and fewer failures, the efficiency strategy gains credibility. If the benefits remain confined to demos or internal claims, the thesis weakens.
Three Signals Will Test the Better Data Strategy
The next stage of the Anthropic OpenAI contest will be judged through operating evidence, not another round of promotional benchmark charts.
The first signal is the status and stated purpose of the reported Decart transaction. A completed agreement would confirm that Anthropic wants direct ownership of optimization technology. A partnership could indicate interest without the risks of full integration.
The most important detail would be how Anthropic deploys Decart’s engineers and software. Placement near Claude inference, training systems, or hardware strategy would strengthen the efficiency interpretation. A focus on standalone media products would weaken it.
Readers should look for measurable changes after any agreement. Faster Claude responses, higher availability during demand spikes, or more capable agents operating within similar resource limits would connect corporate strategy to product outcomes.
The second signal is product-level efficiency across Anthropic and OpenAI. New models should be evaluated at a fixed capability level, not merely against the strongest available benchmark. The question is how cheaply and reliably each provider completes comparable work.
Model routing will be part of that evidence. A provider can reduce costs by assigning routine requests to smaller systems and escalating difficult tasks. Successful routing must preserve accuracy while avoiding unnecessary calls to frontier models.
Long-running agents offer a demanding test. They combine reasoning, retrieval, tool use, and repeated verification. Small inefficiencies compound across every step, making agent completion rates more informative than isolated chat responses.
Developers should watch latency and reliability alongside model quality. A coding system that reasons well but repeatedly times out does not create an efficient workflow. A faster model that introduces more defects also fails the test.
Enterprise adoption provides another useful signal. Buyers will expand usage when AI systems deliver predictable value within governance and budget constraints. Pilot announcements matter less than recurring use across real business processes.
The third signal is greater disclosure about training data and evaluations. Complete transparency is unlikely because the labs treat data mixtures and optimization methods as competitive assets. More specific reporting could still improve outside assessment.
Useful disclosures would describe how companies test synthetic data, prevent benchmark contamination, and evaluate unfamiliar tasks. Reports should also distinguish gains from model changes, retrieval systems, and product-layer routing.
OpenAI and Anthropic have reasons to keep these details private. Revealing a high-value data recipe could help competitors reproduce it. However, vague claims make it difficult for customers to assess reliability and risk.
Independent evaluations can narrow that gap. They should use private test sets, realistic workflows, and outcome-based measures. They should also report variability rather than presenting one average score as a complete judgment.
These three signals follow a clear order. First, watch whether Anthropic converts reported interest into an infrastructure commitment. Second, examine whether that commitment changes product economics and reliability. Third, demand evidence explaining where the gains originated.
A completed deal without product improvements would weaken the strategy. Better Claude economics without a deal would show that Anthropic found another path. Strong data and evaluation disclosures would make either outcome easier to interpret.
For developers, the practical response is to benchmark workflows rather than brands. Test representative tasks, measure retries, and include review time. Keep retrieval sources clean and record where generated answers fail.
Enterprise buyers should ask providers how models use company information, how frequently retrieval indexes update, and how access controls apply. They should also compare total task completion costs rather than published token rates alone.
Knowledge workers face a similar choice. A newer model can help, but the quality of the documents supplied to it often determines the answer. Organizing trusted context remains valuable even as frontier models improve.
Anthropic and OpenAI will continue releasing better models. The more consequential contest now concerns which company turns intelligence into dependable, affordable work. Watch the Decart talks, deployed efficiency, and data disclosures. Together, those signals will show whether better data and infrastructure truly outweigh another cycle of scale.


