Connect with us

Artificial Intelligence

OpenAI Presence: The Enterprise AI Agent Product That Comes With Engineers Attached

Published

on

OpenAI Presence enterprise AI agents

OpenAI’s New Enterprise AI Agent Play: A Managed Service, Not a Self-Serve Product

On July 22, OpenAI announced Presence, a managed enterprise AI agent offering that breaks from the company’s usual playbook. You can’t just sign up online and start using it. Presence is delivered through a limited general availability programme, with deployments led by OpenAI’s own Forward Deployed Engineers and a handful of selected global systems integrators.

This is a notable shift for a company that’s built its business on API keys and seat licences. Presence is sold as a project, not a product. Each engagement starts with a single, focused job — resolving a billing dispute, handling an insurance claim, or clearing an employee IT service request.

The agent gets only the knowledge and system access that specific job requires. The customer writes the rules: what the agent can do, when it needs sign-off, and when a human takes over. After launch, Codex reads production sessions and escalations, then proposes changes that the customer’s team tests and approves before rollout.

The Labour Behind the AI Agent

OpenAI’s documentation is refreshingly candid about the work involved. Its help centre lays out a six-stage process: scoping business outcomes, security and privacy review, legal review, simulation and acceptance testing, staged rollout, and post-launch iteration. A Presence agent, it says, does not become production-ready simply by ingesting documents.

That honesty matters. Gartner has warned that more than 40% of agentic AI projects will be cancelled by the end of 2027. The failures, Gartner says, stem from governance, undefined business value, and weak operational discipline — not from model capability.

Almost everything Presence bundles is aimed squarely at that diagnosis. Simulations and graders test whether an agent reached the right outcome, followed policy, used its tools correctly, and escalated when it should — before anyone outside the company speaks to it. Guardrails intervene when an interaction moves past defined boundaries. Session records and action histories give reviewers something to audit. Escalation paths hand a person structured context rather than a cold transcript. New versions go out through controlled rollout with rollback.

Enterprises have spent two years learning that the hard part of a production agent sits in integration, permissions, and change management. A vendor that sends engineers to do that work is responding to what buyers have actually been failing at, rather than shipping another dashboard and calling the gap a customer problem.

Where the Constraint Sits: Forward Deployed Engineers

The trade-off shows up in the eligibility criteria. Access, OpenAI says, depends on workflow fit, implementation readiness, and available delivery capacity.

Delivery capacity is a consulting constraint. Software scales; engineers cleared into a bank’s core systems do not. The title Forward Deployed Engineer is borrowed from Palantir, where it describes staff embedded in customer operations for months at a time. The economics attached to it look nothing like the economics of metered inference.

By putting its own FDEs and named partners at the front of every deployment, OpenAI has stepped into the layer of the market occupied by the integrators it will also rely on to scale. That’s a workable arrangement while volumes are small — and a more complicated one later.

It also raises a question for anyone scoping a contract. When the model vendor is also the implementation partner, the lines of accountability for a policy misapplied in production need to be written down rather than assumed.

The Enterprise AI Agents on Display Are Still Early

OpenAI describes Presence as battle-tested. Its case for that language: the product was assembled from years of deploying agents with enterprise customers before it was packaged and named. The claim is about accumulated practice rather than time in market, and it’s a reasonable one to make.

The strongest single proof point is OpenAI’s own English-language phone support line, 1-888-GPT-0090. The company says the agent met or exceeded internal benchmarks for frontline human support within weeks, now resolves 75% of inbound issues without human assistance, and cut human handoffs by 15 percentage points in ten days through the Codex improvement loop.

Those are OpenAI’s figures, measured against OpenAI’s own grading criteria, on OpenAI’s own channel. The transparency is welcome, but the numbers are not independently verified.

The three named customers sit earlier in the cycle than the launch framing implies. BBVA is exploring voice support for everyday banking in Mexico. SoftBank is testing Japanese-language conversations. IAG is exploring support during high-demand events such as severe weather. Daniel Ordaz, head of AI transformation at BBVA Mexico, describes the bank as a design partner helping shape and refine voice experiences for financial customer service. Design partners are normal and useful at limited GA. None of the three, though, is presented as running Presence at scale — worth holding alongside the word proven.

What OpenAI Hasn’t Disclosed About Presence

Pricing is not published. Implementation scope and cost are set per customer and per deployment. That’s ordinary for enterprise services, but it leaves buyers without a public reference point for cost per resolved contact against an incumbent contact-centre vendor.

The model is not named. Presence uses OpenAI models, the documentation says, with configuration selected for the workflow and subject to change as that workflow evolves. That flexibility is defensible engineering — pinning a production agent to a frozen model version ages badly. Teams that have spent the past year building evaluation suites against specific versions will nonetheless want the contract to say what they’re being held to when the configuration moves.

Channel support during limited GA covers voice or chat, with contact-centre integration, routing, authentication, and handoff design confirmed deployment by deployment. Data handling follows the same pattern, with the signed architecture and contract treated as the governing record rather than any published policy.

Presence sits apart from ChatGPT Workspace Agents, which remain the self-serve path for teams building inside ChatGPT and Slack. Voice customers keep API access to OpenAI’s frontier models. The company now offers broadly the same capability three ways, separated less by what the technology can do than by who does the work.

That leaves buyers choosing on delivery capacity as much as on model capability. And on OpenAI’s own account, delivery capacity is the part being rationed.

For a deeper look at how companies are putting agentic AI to work, see our coverage of HP accelerating enterprise workflows with OpenAI Frontier and the broader enterprise AI agent landscape.

Continue Reading

Artificial Intelligence

XDOF, three months out of stealth, is already closing in on a $1.2B Series B

Published

on

XDOF Series B

From stealth to unicorn talk in record time

Three months. That’s how long XDOF has been out in the open. And already, the robotics data startup is in late-stage conversations to raise a Series B at a valuation hovering around $1.2 billion, according to multiple sources familiar with the negotiations. The round would be led by 8VC.

Not bad for a company that didn’t even exist publicly until June.

XDOF was co-founded in 2024 by UC Berkeley researchers Philipp Wu (CEO) and Fred Shentu (CTO). Their origin story traces back to a research project called GELLO — a low-cost teleoperation system that lets a human operator control a robotic arm from a distance. The goal? Generate training data for robots. That work produced an influential paper in robotics and, eventually, a company.

The startup’s Series A, a $70 million round announced in June, drew participation from Thrive Capital, Andreessen Horowitz, Lux, and Spark Capital. At the time, XDOF wasn’t planning to raise again so soon. But the market had other ideas.

Why investors are knocking on XDOF’s door

The reason for the sudden interest? Growth. Real, measurable growth.

XDOF’s annualized revenue is approaching $50 million, sources say. That kind of traction, so soon after a Series A, tends to make venture capitalists sit up and take notice. It also tends to make them pick up the phone.

“They weren’t out raising,” one person familiar with the situation told TechCrunch. “The VCs came to them.”

Terms aren’t final, and the total capital being raised remains unclear. TechCrunch couldn’t confirm whether the $1.2 billion valuation includes the new funding or sits on top of it. Both XDOF and 8VC declined to comment.

The Scale AI for physical robots

XDOF’s pitch is straightforward: it builds the data pipelines, collection tools, and annotation systems that frontier AI labs and robotics companies would rather not build themselves. Think of it as an outsourced data-supply chain for the robotics industry.

Investors describe XDOF as the Scale AI or Mercor of physical robotics — a nod to the data-labeling giants that powered the AI boom. The comparison makes sense. Large language models trained on the entire internet. Physical robots? They don’t have that luxury. There’s no massive, ready-made dataset of real-world robot interactions sitting online. That scarcity makes data collection the critical bottleneck on the road to general-purpose machines.

Wu felt that bottleneck firsthand as a PhD student. His research on how robots learn from large datasets kept hitting the same wall: “large-scale data to work with” simply didn’t exist, he told TechCrunch in June.

Building the ABC dataset

XDOF is tackling that problem head-on. The startup is partnering with UC Berkeley’s AI Research lab to release what it believes is the largest collection of high-quality robot training data ever assembled. The dataset is called ABC.

Collecting that data requires a hybrid approach. XDOF combines remote robot teleoperation with human collectors who wear sensors to record everyday tasks. Think folding clothes. Flattening boxes. The mundane, physical chores that robots still struggle to master.

The company plans to hire and train teams of data collectors around the world. Two main roles are emerging:

  • Teleoperators who steer robots remotely to demonstrate tasks
  • Egocentric operators who wear body sensors to capture natural movement data

Early traction and the competitive landscape

XDOF has already signed up 20 customers, including several frontier AI labs, according to previous statements to TechCrunch. That customer base, combined with the revenue trajectory, helps explain the valuation chatter.

But XDOF isn’t alone in this niche. Other startups chasing real-world data for robot training include Mecka AI. And the human-data platforms that started with LLMs — like Scale AI and Micro1 — are expanding beyond text and images into physical domains.

The race to build the data infrastructure for physical AI is heating up. Whoever wins it will effectively control the fuel supply for the next generation of robots. That’s a position worth paying up for.

Whether the $1.2 billion valuation holds remains to be seen. Deals at this stage can shift. But the fact that XDOF is even in this conversation — three months after emerging from stealth — says something about the demand for what it’s building.

For more on how data is shaping the future of AI, check out AI data labeling trends and robotics funding rounds in 2024.

Continue Reading

Artificial Intelligence

New York City Pulls AI From Younger Classrooms—Here’s Why It Matters

Published

on

NYC AI ban

New York City Just Hit Pause on AI in Classrooms

New York City Public Schools is drawing a hard line: no generative AI for students from 2-K through eighth grade during the 2026-2027 school year. That’s over half a million kids walking into classrooms next week without access to AI-powered tools.

The district says it will remove software with student-facing AI features and block AI companion chatbots. High schoolers? They’re exempt. This isn’t a blanket ban—it’s a targeted move to decide when kids should actually start using the technology.

Mayor Zohran Mamdani put it bluntly: “The tech industry wants us to believe that AI-powered early education is not only inevitable, but necessary. We do not see it that way.”

Why NYC Is Worried About AI for Younger Students

The fear isn’t just that a kid will ask ChatGPT to write an essay. City officials want younger students to build core skills—critical thinking, creativity, communication—without leaning on AI as a crutch. They’re also pushing for stronger human connections in classrooms, not another screen.

Schools Chancellor Kamar Samuels said the city refuses to assume that innovation automatically equals more technology in front of students. It’s a deliberate slowdown, and it follows last year’s bell-to-bell cellphone ban that already limits device use during school hours.

What Happens When Kids Reach High School?

AI doesn’t vanish once students hit ninth grade. Instead, the district plans to roll out AI literacy classes twice a year. The goal? Teach teenagers how to think critically about the technology before they become dependent on it.

That’s a different approach from just saying no. It’s about timing—letting younger minds develop without AI, then giving older students the tools to question it.

The National Battle Over AI in Education

NYC’s decision sits at the center of a much bigger fight. The White House has pushed educators to embrace AI responsibly. Some teachers already use it to craft lesson plans, give feedback, or break down tough subjects. But not everyone’s on board.

The Department of Health and Human Services recently gathered childhood experts to talk about excessive screen time. Officials have also called for tougher safeguards around social media and AI. The message? Kids are spending too much time in front of screens, and AI might make it worse.

A Bold Experiment With Zero AI

Here’s what makes NYC’s move so interesting: instead of asking how much AI younger students should use, the largest school district in the country is starting with none. For one academic year, they’re testing whether classrooms are better off with AI kept outside the door.

That’s a radical stance, and it’s not without critics. Some educators argue AI can personalize learning or help struggling students catch up. But NYC is betting that a year without AI will reveal what kids actually need—not what tech companies think they need.

What This Means for Parents and Teachers

If you’re a parent in NYC, expect changes. AI-based apps may disappear from your child’s school day. Teachers will need to plan lessons without generative AI tools. And students in grades 2-K through 8 will rely more on traditional methods—paper, pencils, and human interaction.

For teachers elsewhere, this could be a signal. NYC is the biggest district to take this stance, and its findings could shape policies nationwide. The next year will be watched closely by educators, policymakers, and tech giants alike.

What Happens Next?

The district will spend the year studying how generative AI affects students before deciding what comes next. That research could lead to a permanent ban, a partial rollout, or something entirely different.

For now, NYC is making a statement: childhood shouldn’t be an AI beta test. Whether that’s the right call or a step backward, we’ll know more in 2027. Until then, the debate over AI in schools just got a lot more interesting.

If you’re curious about how AI is shaping other areas, check out our take on AI in education trends or classroom technology policies.

Continue Reading

Artificial Intelligence

Meta’s Muse Spark 1.3 takes on GPT-5.6 and Claude — but can it really win?

Published

on

Muse Spark 1.3

Meta just fired a serious shot in the AI arms race

The company quietly unleashed Muse Spark 1.3, its most advanced AI model to date, and it’s aiming straight at the top dogs. Developers can already access and pay for the update, which Meta says represents a massive leap forward in performance.

It won’t stay confined to the developer sandbox for long. Over the coming weeks, the model will roll out across Instagram, Facebook, and the Meta AI assistant — putting it in front of billions of everyday users.

What makes Muse Spark 1.3 actually different?

Meta’s Chief AI Officer, Alexandr Wang, didn’t mince words. He called this “the biggest jump so far on model performance,” pointing to serious gains in two areas: coding and agentic tasks — the kind where the AI acts on your behalf rather than just answering questions.

But here’s the catch. Wang told Bloomberg that Muse Spark 1.3 is competitive with Anthropic’s Claude Fable 5.1 and even beats OpenAI’s GPT-5.6 Sol at coding. That’s a bold claim, especially with OpenAI’s upcoming Astra model lurking in the wings.

Take those comparisons with a grain of salt, though. Benchmarks can be gamed, and a model that crushes one test might stumble on a totally different task. Real-world performance is what actually matters.

Efficiency gains under the hood

Wang broke down a few upgrades that set Muse Spark 1.3 apart:

  • 25% fewer tokens needed to complete the same job — meaning lower costs and faster responses
  • Multi-workflow handling — it can juggle several tasks at once instead of forcing separate sessions
  • Better context retention across long, complicated instructions
  • Self-awareness of limits — the model now pauses to ask for clarification before taking any irreversible action

That last point is quietly important. AI that knows when it doesn’t know is a big step toward trustworthiness, especially for agentic use cases.

Pricing stays flat, adoption explodes

Here’s something developers will appreciate: Meta isn’t raising prices. Muse Spark 1.3 costs the same as its predecessor, Muse Spark 1.2. That’s a smart move when rivals are hiking rates.

Wang told Bloomberg that adoption on Meta’s developer platform has been strong — some users are burning through trillions of tokens every week. Those numbers suggest real usage, not just hype.

What about open-source fans? Meta hasn’t decided whether it will release the model’s weights — the blueprint that lets outside developers build on top of it. The older Muse Spark 1.2 weights are still headed for release, but the new model’s future remains unclear.

The bigger picture: Meta’s spending spree continues

Meta is still pouring billions into AI infrastructure, and Muse Spark 1.3 is the clearest signal yet that the company believes it’s closing the gap with OpenAI and Anthropic. Whether that’s true or just corporate bravado will play out in the benchmarks and real-world deployments over the coming months.

For now, the model is available to developers, and the app rollout is imminent. If you’re building on Meta AI tools, this update is worth a serious look. And if you’re just a curious user, you’ll likely meet Muse Spark 1.3 in your Instagram feed sooner than you think.

One thing’s certain: the AI race just got a lot more interesting.

Continue Reading

Trending