The Assistant SDK for iOS
An AI assistant in your iOS app.
Real SwiftUI.
The Assistant SDK drops a governed agent into your app: it answers in your own UI, not a chat window — real SwiftUI built from the components and APIs you already have. Swift Package, install today.
Start Free
iOS SDK Docs
Real SwiftUI. Not a webview.
Every response renders as native SwiftUI from a single BindJS definition. Native gestures, native animation, dynamic type, accessibility. 60 FPS.
View on GitHub · Apache 2.0
SwiftUI on iOS.
Dynamic type, VoiceOver, and accessibility behave like the rest of your app — because it is the rest of your app.
One definition, identical everywhere.
Same schema, same validation, same allowlist on every surface. The agent can't render on Android what you didn't approve on iOS.
Test on real devices.
Any component, content, or full MCP App gets a preview link. iOS opens it as an App Clip, real SwiftUI on the phone in your hand, no install. Android opens the preview app. Web opens the browser. Your first preview is minutes after signup.
A governed agent in your own app.
It follows your scripts, stays on brand, and can only render components you approved. Schema validation on every render, identically on every platform.
Your key, server-side.
Anthropic, OpenAI, or Gemini, configured once in the agent proxy. The key stays on the server and never ships in your client, and every call through the proxy lands in your tool-call stats and Langfuse traces.
The MCP Apps protocol, handled.
Tool calls, streaming responses, and schema validation on every render. The SDK implements the spec and keeps up with it, so your app wires up a view instead of a protocol.
It follows your scripts.
Greet like this. Ask X before Y. Never leave the catalog. The agent holds to the script you author, on every turn.
Start from a working app.
Clone the retail sample, point it at your APIs, and run the whole agent inside your own app. Your design system carries over; only the syntax changes.
Retail
Finance
Common Questions
The Assistant SDK for iOS
An AI assistant in your iOS app.
Real SwiftUI.
The Assistant SDK drops a governed agent into your app: it answers in your own UI, not a chat window — real SwiftUI built from the components and APIs you already have. Swift Package, install today.
Start Free
iOS SDK Docs
Real SwiftUI. Not a webview.
Every response renders as native SwiftUI from a single BindJS definition. Native gestures, native animation, dynamic type, accessibility. 60 FPS.
View on GitHub · Apache 2.0
SwiftUI on iOS.
Dynamic type, VoiceOver, and accessibility behave like the rest of your app — because it is the rest of your app.
One definition, identical everywhere.
Same schema, same validation, same allowlist on every surface. The agent can't render on Android what you didn't approve on iOS.
Test on real devices.
Any component, content, or full MCP App gets a preview link. iOS opens it as an App Clip, real SwiftUI on the phone in your hand, no install. Android opens the preview app. Web opens the browser. Your first preview is minutes after signup.
A governed agent in your own app.
It follows your scripts, stays on brand, and can only render components you approved. Schema validation on every render, identically on every platform.
Your key, server-side.
Anthropic, OpenAI, or Gemini, configured once in the agent proxy. The key stays on the server and never ships in your client, and every call through the proxy lands in your tool-call stats and Langfuse traces.
The MCP Apps protocol, handled.
Tool calls, streaming responses, and schema validation on every render. The SDK implements the spec and keeps up with it, so your app wires up a view instead of a protocol.
It follows your scripts.
Greet like this. Ask X before Y. Never leave the catalog. The agent holds to the script you author, on every turn.
Start from a working app.
Clone the retail sample, point it at your APIs, and run the whole agent inside your own app. Your design system carries over; only the syntax changes.
Retail
Finance
Common Questions
The Assistant SDK for iOS
An AI assistant in your iOS app.
Real SwiftUI.
The Assistant SDK drops a governed agent into your app: it answers in your own UI, not a chat window — real SwiftUI built from the components and APIs you already have. Swift Package, install today.
Start Free
iOS SDK Docs
Real SwiftUI. Not a webview.
Every response renders as native SwiftUI from a single BindJS definition. Native gestures, native animation, dynamic type, accessibility. 60 FPS.
View on GitHub · Apache 2.0
SwiftUI on iOS.
Dynamic type, VoiceOver, and accessibility behave like the rest of your app — because it is the rest of your app.
One definition, identical everywhere.
Same schema, same validation, same allowlist on every surface. The agent can't render on Android what you didn't approve on iOS.
Test on real devices.
Any component, content, or full MCP App gets a preview link. iOS opens it as an App Clip, real SwiftUI on the phone in your hand, no install. Android opens the preview app. Web opens the browser. Your first preview is minutes after signup.
A governed agent in your own app.
It follows your scripts, stays on brand, and can only render components you approved. Schema validation on every render, identically on every platform.
Your key, server-side.
Anthropic, OpenAI, or Gemini, configured once in the agent proxy. The key stays on the server and never ships in your client, and every call through the proxy lands in your tool-call stats and Langfuse traces.
The MCP Apps protocol, handled.
Tool calls, streaming responses, and schema validation on every render. The SDK implements the spec and keeps up with it, so your app wires up a view instead of a protocol.
It follows your scripts.
Greet like this. Ask X before Y. Never leave the catalog. The agent holds to the script you author, on every turn.
Start from a working app.
Clone the retail sample, point it at your APIs, and run the whole agent inside your own app. Your design system carries over; only the syntax changes.
Retail
Finance
Common Questions