Corti is designed to meet customers where they are in their technical journey. Whether they want a deep integration or a no-fuss solution that works out of the box, we offer multiple ways to get started with our AI. Here’s a breakdown of the four primary interaction models, arranged from most integrated (and flexible) to least integrated (but fastest to launch):
Pure API Integration
Most flexible, most development work
For tech-savvy teams looking to build custom experiences, Corti's API offers full control over how our AI is embedded into their workflows.
Ideal for: Engineering teams with strong internal dev capabilities.
Benefits: Maximum customization and adaptability.
Considerations: Requires the most development effort on the customer side.
SDK Integration
Simplifies building on our API
Our SDKs reduce the complexity of building on top of the API by providing helpful abstractions and ready-made components.
Ideal for: Teams that want to accelerate development without sacrificing control.
Examples: Our Dictation SDK, with more SDKs in development.
Benefits: Faster time to value, reduced dev effort.
Embedded Corti Assistant in Customer Apps
Feels like part of the customer’s system
We support embedding Corti Assistant directly into customer applications using iFrame or WebView technologies.
User experience: Seamless. Feels native to the customer’s platform with no Corti branding or separate login.
Important note: This is not "white-labelling" — customers can customize the feel, but Corti branding can’t be removed entirely for now.
Benefits: No context switching for users, faster adoption.
Standalone Corti-Branded Apps
No integration required
Customers can use Corti’s applications—like Corti Assistant or Mission Control—as standalone platforms. Users simply log in, use the tools, and paste outputs into their existing systems.
Ideal for: Teams who want to get started with zero technical lift.
Benefits: Fastest time to value, low barrier to entry.
Considerations: May require more manual effort to copy results into other systems.
Choosing the Right Model
The right option depends on the customer’s technical capacity, time-to-value expectations, and workflow preferences. Use this spectrum to guide conversations and align customer needs with the best-fit approach.
Have a question for our team?
Click Support in the bottom-left corner of the console to submit a ticket or reach out via email at [email protected] and we'll be happy to assist you.