AGKit vs Apple Foundation Models
Choose AGKit when your app needs an agent runtime for application actions, with model routes and operations managed centrally through Cloud.
Apple’s framework provides model sessions, guided generation, and custom tools. Availability depends on the device, operating system, and model configuration.
 AGKit | Apple Foundation Models | |
|---|---|---|
| Application stack | Swift, Android, React Native, and Web; one Cloud backbone | Native Apple framework |
| Application actions | Agent runtime, tool contracts, permission hooks, and cancellation | Custom Tool implementations and guided generation |
| Configuration | Cloud-managed model tiers, credentials, and agent profiles | Apple-supported model configurations |
| Production controls | End-user identity, project/user budgets, and configured attestation | Runtime availability and framework-specific requirements |
| Application responsibility | Tool implementation, state validation, approvals, and actual undo | App owns state, approvals, and recovery |
Choose your platform and access path for SDK availability and setup. Guard and confirmation support depends on the SDK execution path you integrate.
Where Foundation Models fits
Your feature is focused on supported Apple devices and benefits from system model integration. Check runtime availability and design the experience for an unavailable or not-yet-ready model.
Where AGKit fits
You want tools and application state connected to an agent runtime, with Cloud managing model routes and operations for your Cloud integration.
What your team implements
Your app implements tools, approval, and recovery. Select an SDK execution path that supports the hooks you need; switching inference location also requires support in the installed client.