28:00

• Four services: search, agent identity, access policy, audit. They run in a new layer above the GraphOS routers and are exposed as MCP tools.
• The layer merges one federated supergraph or many separately built graphs into one catalog, the "domain model".
• Policy is defined centrally on domain-model fields and checked per request against the requesting agent. Examples given: a support agent sees the customer name but not rewards; a marketing agent sees rewards but not the name; a desktop analyst agent can request escalation, approved by a person.
• A rule on a field holds whether the agent asks for it directly, reaches it through an order object, or writes a query nobody anticipated. No per-tool policy.
• The domain model is split into semantics, policy (deterministic, enforced, audited), and guidance (when to make the expensive AS400 inventory call). Available on the day of the keynote.

34:30

• Goal stated as real-time reallocation of paid search spend; one campaign had a $60,000 cost per acquisition, and a recommendation sat for weeks.
• MVP built in Claude Cowork against about 19 custom MCP servers, read and write, with no identity management and single points of failure on individual laptops.
• Framed as the BFF-sprawl problem recurring as agent sprawl. The three gaps named: on whose behalf the agent acts, what it may see and do, and what happened afterwards (identity, policy, audit).
• Reported results: double-digit improvements in cost per acquisition and incremental return on ad spend; pilot done in under 90 days. No baseline given.

45:00

• Factory takes API docs or an OpenAPI/Swagger spec, walks a modeler through design decisions, and emits an Apollo Connectors subgraph for the router.
• Each decision is recorded with its sources in git, so a later API change or a new API is checked against earlier choices, and hand-offs between modelers keep the same rationale. Ships as a skill in Apollo's skills collection on GitHub.
• The GraphOS MCP server now covers most of GraphOS and Studio, writes included: building graphs, schema checks, graph health, proposals. Listed in the ChatGPT and Claude marketplaces.
• Rover gains contract management, client operation checks and an expanded plugin system. GraphOS Desktop shown as an unreleased preview.

50:00

The captions render the company as "Enable": cybersecurity and IT management, millions of managed devices, grown by acquisition. That matches N-able; the name was not checked.

• Acquisitions left systems that disagreed on what a device was; a backup-status question could hit several APIs. "Project Fusion" unified them into one graph API.
• After Apollo's MCP server shipped, the whole API was opened to agents in about two months, with no rebuild, because the graph was already designed and documented.
• A prospect's own agent ran a comparison against a competitor and recommended them; the deal was won. "Your number one API client isn't a developer anymore. It's an agent."

58:00

• First preview release of Router 3. The request pipeline is refactored into layers with single responsibilities; in Router 2, a change to metrics touched many services. The stated aim is the tail (P99 and above), not the median, and smaller change surfaces for agent-written changes.
• New query planner adapted from beam search in the literature. Across a corpus of the most complex customer graphs: 20x faster planning and 20x less memory. Worst operation went from 28 s to 90 ms.
• Circuit breaking for struggling subgraphs, to avoid congestive collapse, lands for GA; distributed rate limiting follows. Native Rust plugin interface changes before GA, target end of year; Apollo asked for production feedback since it lacks customers' extensions and configs.
• Operations context: incidents down 34% year over year; support reproduces 9 of 10 reported issues before escalation and ships 11x more direct fixes; 2 trillion operations a month through GraphOS.
• Also listed: graph artifacts for rollbacks, canaries and blue-green publishing; Swift 6 support with a 75% speed-up the captions render as "decalization", likely deserialization, on iOS.