Foundation Models framework — the unified API for third-party cloud providers

The 2026 framework lets apps call cloud models like Claude and Gemini (or "any provider that conforms to Apple's Language Model protocol") through the same Swift API as the on-device model.

  • What exactly must a provider implement to conform to the Language Model protocol, and can developers register a custom/self-hosted endpoint and their own API keys, or is routing limited to an Apple-curated provider list?
  • Does the unified API normalize provider-specific capabilities — tool/function calling formats, system-prompt handling, streaming tokens, JSON/structured output, multi-turn state — or do these degrade to a lowest common denominator across providers?
  • When a request is routed to a third-party cloud model, what is the data path and privacy boundary? Does it transit Private Cloud Compute, or go direct to the provider, and what is disclosed to the user about where their prompt is processed?
  • If an app supplies a conforming provider, does that provider become selectable by Siri AI for system actions, or is custom-provider routing confined to in-app LanguageModelSession use only?
  • With the framework slated to open-source this summer, will the provider/protocol surface be stable enough to build against now, or should developers expect breaking changes between the beta and the open-source release?
Answered by Frameworks Engineer in 892957022

I believe all of your question about the LanguageModel protocol can be answered in this WWDC26 session - https://developer.apple.com/videos/play/wwdc2026/339

I believe all of your question about the LanguageModel protocol can be answered in this WWDC26 session - https://developer.apple.com/videos/play/wwdc2026/339

Foundation Models framework — the unified API for third-party cloud providers
 
 
Q