# voice.md

## Communication Style

### Overall tone and personality
api.video's voice is **practical, empowering, and authoritative**, yet **approachable** for its developer and business audience. We are **confident** in our technology, **efficient** in our solutions, and **enthusiastic** about innovation, especially concerning AI and video. Our communication aims to simplify complex video infrastructure, making it accessible and impactful for builders.

### Key stylistic elements and patterns
*   **Benefit-Oriented:** We always link features to tangible user benefits, emphasizing what users can *achieve*.
*   **Concise & Direct:** We get straight to the point, using clear and unambiguous language.
*   **Action-Oriented:** We employ strong verbs that inspire action and highlight capabilities.
*   **Emphasis on Simplicity & Efficiency:** Phrases like "in just minutes," "single API," and "no more juggling multiple APIs" are common.
*   **Credibility through Data:** We use numbers and statistics (uptime, playback speed, traffic) to back our claims.
*   **Technical yet Accessible:** We use necessary technical jargon but explain its value and impact clearly, avoiding unnecessary complexity.
*   **Forward-Looking:** We highlight innovation, particularly in AI, and future possibilities.

### Vocabulary preferences and word choices
*   **Tech-forward:** API, SDKs, encoding, CDN, infrastructure, analytics, live streaming, on-demand, AI, transcription, summarization.
*   **Benefit-driven:** Maximize, optimize, simplify, secure, empower, efficiency, insights, productivity, enhance, accelerate.
*   **Speed & Performance:** Lightning-fast, instant, low-latency, real-time, rapid.
*   **Simplicity & Ease:** Simple, all-in-one, quickstart, low-code, seamless, effortless.
*   **Impactful:** Powerful, robust, cutting-edge, innovative, transformative.

## Content Patterns

### Common themes and topics
*   **Video Infrastructure & Management:** Upload, host, manage, deliver, and protect videos and streams.
*   **AI for Video:** Transcription, summarization, analytics, and future AI features.
*   **Developer Experience:** Ease of integration, SDKs, quickstart guides, and diverse tech stack compatibility.
*   **Performance & Scalability:** Uptime, playback speed, global reach (CDN).
*   **Use Cases:** How api.video powers online learning, social apps, e-commerce, communication, and generative AI platforms.
*   **Product Updates & Company News:** Announcing new features, upgrades, and milestones.
*   **Industry Trends:** Insights into video production, authentication, and general video technology.

### Structural approaches to content
*   **Problem-Solution:** Identifying user challenges and positioning api.video as the streamlined solution.
*   **Feature-Benefit:** Clearly outlining what a feature does and the direct advantage it provides.
*   **How-to/Tutorials:** Step-by-step guides for implementation and best practices (especially in blogs).
*   **Bulleted Lists & Short Paragraphs:** Enhances readability and allows for quick scanning of information.
*   **Strong Headlines & Sub-headlines:** Capture attention and convey the core message immediately.

### Call-to-action styles and patterns
*   **Direct & Clear:** Action-oriented verbs.
*   **Benefit-Reinforced:** Often includes a secondary phrase that adds value or removes friction.
*   **Examples:**
    *   "Get started for free" (often followed by "No credit card required")
    *   "Explore AI features"
    *   "Talk to us"
    *   "Sign up"
    *   "Run Demo"

## Audience Interaction

### How the brand addresses its audience
We address our audience directly using "you" and "your," positioning ourselves as an enabler and partner in their building journey. We speak to them as capable developers, innovators, and business leaders looking for efficient, high-performance video solutions.

### Level of formality and relationship style
Our relationship style is **professional yet collaborative**. While we maintain an expert voice, we are not overly formal or academic. We aim to be helpful and supportive, providing resources and guidance that empower our users to succeed. We strive for an expert-to-peer relationship, especially with developers.

### Engagement and conversation patterns
We engage by inviting exploration ("Discover how...", "Learn about..."), encouraging interaction ("Click 'Run Demo' to see..."), and sharing our excitement for new developments ("We're thrilled to introduce..."). We anticipate user needs and offer solutions proactively.

## Guidelines & Examples

### Do's and don'ts for brand communication

**Do's:**
*   Be direct, clear, and concise.
*   Focus on user benefits and problem-solving.
*   Use action-oriented language that inspires building and innovation.
*   Emphasize simplicity, speed, and efficiency in all video operations.
*   Back claims with data, statistics, or real-world use cases.
*   Explain technical terms in an accessible, value-driven way.
*   Show genuine enthusiasm for new features and product advancements.
*   Address the audience as capable, intelligent builders and decision-makers.

**Don'ts:**
*   Be vague, overly complex, or use excessive jargon without context.
*   Sound overly corporate, dry, or impersonal.
*   Focus solely on features without explaining the corresponding benefits.
*   Make unsupported claims or exaggerate capabilities.
*   Use passive voice when active voice is more impactful.

### Example phrases and expressions that are "on-brand"
*   "Integrate on-demand or live-stream videos into your app in just minutes."
*   "Maximize the impact of your videos with powerful built-in AI features."
*   "Discover how our upgraded Analytics delivers deeper insights and better tracking."
*   "Empower any platform with lightning-fast video encoding and a robust CDN."
*   "Simplify your video workflow: no more juggling multiple APIs."
*   "We're thrilled to introduce instant AI transcription and summarization for all your videos."

### Content types and formats the brand uses
*   Blog posts (tutorials, product updates, company news, video trends, case studies)
*   Marketing landing pages
*   Product descriptions and feature pages
*   Documentation (quickstart guides, API references, SDK guides)
*   Demos and interactive tools
*   Customer success stories
*   Email newsletters
*   Social media updates