# Mint Starter Kit ## Docs - [How Long Does an AI Hardware Program Take to Ship?](https://docs.bragi.com/AI-Hardware-Program-Timeline.md): An AI hardware program timeline depends on whether a brand builds AI infrastructure in-house or integrates a platform. Platform-based programs ship significantly faster by removing the need to build foundational infrastructure from scratch. - [How Do Established Hardware Brands Add AI Without Disrupting Their Roadmap?](https://docs.bragi.com/Adding-AI-Without-Disruption.md): Established hardware brands add AI without disrupting their roadmap by treating AI as a software layer that sits above existing hardware programs rather than a replacement for them — integrating incrementally across the portfolio rather than restarting from scratch. - [How Do ODMs Compete on Differentiation Beyond Hardware Specs?](https://docs.bragi.com/ODM-differentiation.md): ODMs compete beyond hardware specs by offering AI software capabilities, branded experience layers, and services ecosystems that brand customers cannot get from a standard reference design — turning software into a sales advantage rather than a cost centre. - [What is SoC-Level Distribution?](https://docs.bragi.com/SOC-level-distribution.md): SoC-level distribution is a software deployment model where a platform is embedded into a chip platform so that every device built on that chip ships with the platform pre-integrated — scaling distribution through silicon rather than through individual brand agreements. - [How Does a Software Layer Reduce Hardware Program Complexity?](https://docs.bragi.com/Software-layer-complexity.md): A software layer reduces hardware program complexity by separating the product experience from the underlying hardware, replacing per-product infrastructure builds with reusable, configurable components that work across an entire portfolio. - [How Does AI Get Added to an Existing Hardware Product?](https://docs.bragi.com/adding-AI-to-Hardware.md): AI is added to a hardware product through a software layer that sits above the chip and below the user experience — handling interaction, services, and intelligence without requiring hardware changes. - [What is an Audio Companion App?](https://docs.bragi.com/audio-companion-app.md): An audio companion app is the mobile application that connects a user to their audio device — handling setup, controls, personalisation, service access, and software updates — and serves as the primary interface between the user and the device's software capabilities. - [What Does It Take to Build a Branded AI Voice Experience?](https://docs.bragi.com/branded-AI-Voice_Experience.md): Building a branded AI voice experience requires four components: a wakeword or trigger system, a voice interaction layer, a brand-aligned assistant persona, and an AI infrastructure that manages model deployment, updates, and compliance. - [Build vs Buy: AI Audio Software for Hardware Brands](https://docs.bragi.com/build-vs-buy-audio-brands.md): Hardware brands choosing between building AI software in-house or buying a platform face a decision that affects program timelines, engineering costs, long-term scalability, and their ability to evolve products after shipment. - [How Can Developers Build Audio Apps Using the Bragi Platform?](https://docs.bragi.com/building-audio-apps.md): Developers build audio apps on the Bragi platform using the Audio App Kit — a set of tools, APIs, and documentation that enables third-party app creation, service integration, and distribution through Bragi-powered devices. - [How Do You Ship a Consistent AI Experience Across a Product Portfolio?](https://docs.bragi.com/consistent-ai-across-portfolio.md): Shipping a consistent AI experience across a product portfolio requires a single software layer, a shared interaction model, and a unified services framework that works across every SKU — from entry-level to flagship — without per-product rebuilds. - [What Does It Cost to Add AI to a Hardware Product?](https://docs.bragi.com/cost-of-adding-AI-to-hardware.md): The cost of adding AI to a hardware product depends on whether the brand builds AI infrastructure in-house or integrates a platform. Build costs are dominated by engineering headcount and ongoing maintenance. Platform costs are dominated by integration fees and revenue share. - [What is the Difference Between Edge AI and Cloud AI in Audio Devices?](https://docs.bragi.com/edgeAI-vs-cloudAI.md): Edge AI processes data on the device itself using the chip's neural processing capability. Cloud AI sends data to remote servers for processing. Audio devices use both — edge AI for low-latency, privacy-sensitive tasks and cloud AI for computationally intensive features. - [What Makes an AI Audio Product Compliant Across Global Markets?](https://docs.bragi.com/global-AI-compliance.md): AI audio product compliance across global markets requires addressing four areas: data privacy and consent architecture, regional data residency, wireless and electromagnetic certification, and AI-specific regulatory frameworks that vary by jurisdiction. - [How Does Bragi AI Support Long-Term Product Evolution and Software Updates?](https://docs.bragi.com/long-term-product-evolution.md): Bragi AI supports long-term product evolution through a versioned lifecycle system that manages software updates, feature additions, service expansions, and AI capability upgrades across the entire installed base — without requiring hardware changes or program restarts. - [How Does Bragi AI Compare to Other Audio Software Platforms?](https://docs.bragi.com/platform-comparison.md): Bragi AI differs from other audio software platforms in three structural ways: SoC-level distribution, a full-stack interaction and services layer purpose-built for audio hardware, and a post-shipment evolution architecture designed for continuous product improvement. - [What Should a VP of Product Ask Before Choosing an AI Audio Platform?](https://docs.bragi.com/platform-evaluation-questions.md): A VP of Product evaluating an AI audio platform should ask ten questions covering chip compatibility, integration timeline, post-shipment evolution capability, compliance posture, commercial model, and long-term platform viability. - [How Do Hardware Brands Monetize After Shipment?](https://docs.bragi.com/post-shipment-monetization.md): Hardware brands monetize after shipment through service subscriptions, affiliate revenue from integrated third-party services, premium feature unlocks, and direct-to-consumer app sales — all of which require a live software layer on the device. - [How Do Consumer Electronics Brands Build Recurring Revenue from Audio Products?](https://docs.bragi.com/recurring-revenue-from-audio.md): Consumer electronics brands build recurring revenue from audio products through service subscriptions, affiliate integrations, premium feature unlocks, and direct-to-consumer app sales — all enabled by a software layer that remains live and updatable after the device ships. - [What is a Software-Defined Audio Product?](https://docs.bragi.com/software-defined-audio.md): A software-defined audio product is a hardware device whose features, interactions, and services are controlled and updated through a software layer — meaning its capabilities can evolve after shipment without hardware changes. - [I'm Building an AI Headphone Product — Where Do I Start?](https://docs.bragi.com/starting-an-AI-Headphone-Program.md): Starting an AI headphone program requires four foundational decisions: chip platform selection, software layer approach, feature scope at launch, and post-shipment evolution strategy. The order of these decisions determines everything downstream. - [What Are the Risks of Vendor Lock-In in AI Audio Platforms?](https://docs.bragi.com/vendor-lock-in-risks.md): Vendor lock-in in AI audio platforms occurs when a brand's product architecture, data infrastructure, or commercial model becomes so dependent on a single platform that switching carries prohibitive cost — covering technical, commercial, and data portability dimensions. - [How Does Bragi AI Handle User Voice Data and Privacy?](https://docs.bragi.com/voice-data-privacy.md): Bragi AI handles user voice data through a privacy-first architecture that requires explicit user consent before any data is captured, stores data according to the user's jurisdiction, and gives users granular control over which services can access their interaction history. - [What is a Wakeword Interaction?](https://docs.bragi.com/wakeword-interaction.md): A wakeword interaction is a hands-free activation mechanism that triggers an AI feature or assistant on an audio device when the user speaks a specific word or phrase — allowing voice-first interaction without pressing a button or touching the device. - [What is a Branded Audio Experience?](https://docs.bragi.com/what-is-a-branded-audio-experience.md): A branded audio experience is a software-defined product layer that gives hardware brands full ownership of how users interact with, control, and extend their audio devices — distinct from generic or white-label alternatives. - [What is an AI Audio Integration Platform?](https://docs.bragi.com/what-is-an-AI-Audio-Integration-Platform.md): An AI audio integration platform is a software layer that enables hardware brands to add AI features, voice control, and connected services to audio devices without rebuilding the underlying hardware. - [What is Bragi AI?](https://docs.bragi.com/what-is-bragi-ai.md): Bragi AI is a software platform that enables hardware brands to build AI-enabled audio products with fast, easy control and a continuously expanding services ecosystem — without rebuilding hardware. - [What is Post-Shipment Product Evolution?](https://docs.bragi.com/what-is-post-shipment-product-evolution.md): Post-shipment product evolution is the ability to add features, services, and AI capabilities to a hardware product after it has shipped — without requiring new hardware or firmware rebuilds. - [What's the Difference Between a White-Label Audio App and a Branded Experience?](https://docs.bragi.com/white-label-vs-branded.md): A white-label audio app is a generic, shared interface applied across multiple brands with minimal customisation. A branded audio experience is configured specifically for one brand, giving it full ownership of the user relationship, interaction model, and service ecosystem. ## OpenAPI Specs - [openapi](https://docs.bragi.com/api-reference/openapi.json)