Does "Apple Intelligence" need to be Turned On for this as well?
Apple Foundation Models
21–30 of 244 posts
Re: Apple Foundation Models
#22This seems smart. Apple, despite not really leading in AI themselves, are right on the hot path of where developers are going to yolo slop into the ecosystem. Make a tonne of sense to define a nice clean API that places like Anthropic can build on top of and expose to developers.
It's also smart for them to make sure the billing is going direct from Anthropic to the developer. The initial thought is "That means Apple's not taking a cut", but from the other side of it, developers who use this API are going to have to expose that cost to customers somehow, and that translates to subscription/InAppPurchase etc. on top of which Apple will get it's 30%.
Re: Apple Foundation Models
#23From app developer standpoint why would anyone ship claude keys like that ... or am I missing something? From consumer standpoint - I guess they can use their own keys but it is not something that is very user friendly as you can imagine.
[deleted]
Re: Apple Foundation Models
#24So where does the api key reside? You can’t ship it on the iOS client since anyone can read and abuse it
[deleted]
Re: Apple Foundation Models
#25> Requests go directly from your app to the Claude API; Apple is not in the request path and does not see prompts or responses.
I know this is from a developer perspective. But as a consumer this is just funny.
Re: Apple Foundation Models
#26> Usage is billed to your Anthropic account at standard API pricing.
While expected, it’s still a bummer.
Re: Apple Foundation Models
#27From app developer standpoint why would anyone ship claude keys like that ... or am I missing something? From consumer standpoint - I guess they can use their own keys but it is not something that is very user friendly as you can imagine.
it says:
Proxy (production)
For production, route requests through your own back end with .proxied. The relay at baseURL adds the Claude API credential server-side, so the app ships no key. The headers you provide are sent on every request so your proxy can authorize the caller.
https://platform.claude.com/docs/en/cli-sdks-libraries/libra...
Re: Apple Foundation Models
#28While I'm happy with Apple introducing this abstraction. my main concern was with local models. I'd love using Gemma4 as an example. but thinking of a user. if 10 Apps each uses same model and downloads it, the phone will be bloated. I still didn't understand if Apple provided a way for multiple apps uses same on-device model (without tricky namespaces and permissions). I didn't see anything suggesting that's the cas…
The apps can use the system provided on-device model using the same framework and APIs; but there's no affordances to deduplicate custom models between apps.
Re: Apple Foundation Models
#29While I'm happy with Apple introducing this abstraction. my main concern was with local models. I'd love using Gemma4 as an example. but thinking of a user. if 10 Apps each uses same model and downloads it, the phone will be bloated. I still didn't understand if Apple provided a way for multiple apps uses same on-device model (without tricky namespaces and permissions). I didn't see anything suggesting that's the cas…
That's a great opportunity for Apple to provide a universal unique model ID protocol and some shared storage space to allow devs to register models.
Re: Apple Foundation Models
#30Is this Apple encouraging developers to go through their api abstraction layer to use LLMs so that when they launch their own (which I think we’ve heard they’ve been spending lots of money on training and might be somehow involved with Siri or current Apple AI?) that they can easily help devs make a seamless transition? Or is it just a developer nicety or something else?
This is support for a new framework that ships with reality/mac/iPad/watch/tv/iOS 27 (and that they've promised to open-source later in the year, so presumably you'll also be able to lean on this if you ship Swift on your backend).
The framework's whole deal is that it lets you use the same API to target either the device built-in models, the Apple-hosted online models (Private Cloud Computer), or write your own shims to call out to arbitrarily hosted online models.
You can then dynamically route your calls to a different kind of model/provider, using system APIs, without having to write your own abstraction layer over "I want to use local model for this, but I want to use Claude for that", or having to integrate your own API integration with Anthropic/OpenAI APIs.
It abstracts things like tool calling in one place; and has a bunch of other niceties/oddities (it keeps the same "transcript" going, even if you dynamically switch providers/models during a session) and some other things.