Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
You have a website and a product launch coming up. You need a blog post, a LinkedIn ad, an email sequence, social captions, a product description, and ad copy — all in the same voice. Normally you’d brief a writer, wait days, review for tone consistency, and iterate. This playbook creates a brand voice from your existing website pages, then fires every relevant Generate app against that voice. In one script run you get a full content library — every piece on-brand by construction.Mavera-only. No external API, no CMS integration, no third-party auth. Just Brand Voice + Generate + the Mavera API.
Architecture
What You Need
| Requirement | Details |
|---|---|
| Mavera API key | Starts with mvra_live_. Get one at Developer Settings. |
| Workspace ID | From your dashboard URL (ws_...). |
| 2–5 website URLs | Public pages that represent your brand voice (about page, blog, homepage). |
| Product brief | Topic, audience, and key points for the content you want to generate. |
| Credits | ~200–400 total. See Credits Estimate. |
| Python 3.8+ or Node.js 18+ | requests for Python; native fetch for Node. |
The Flow
Create brand voice from website URLs
POST /brand-voices with 2–5 public URLs. Mavera scrapes them and extracts tone, vocabulary, sentence style, and formality. Poll until status is READY.Discover available generation apps
GET /generation-apps returns every template with its app_id and required input_data fields. Pick the apps that match your content plan.Generate content for each app
Loop through your chosen apps. Every
POST /generations call passes the same brand_voice_id, ensuring consistent voice across blog posts, emails, ads, and social content.Stage 1 — Create Brand Voice from URLs
Stage 2 — Discover Generation Apps
Stage 3 — Generate the Full Library
Every generation passes the samebrand_voice_id. The voice rules constrain tone, vocabulary, and sentence style across all output — blog posts read like your website, emails read like your blog, ads read like your emails.
Variations
Multiple brand voices for audience segments
Multiple brand voices for audience segments
Create separate brand voices for different audiences (e.g. enterprise vs SMB), then run the same content plan against each voice. Compare outputs side by side:
Incremental library updates
Incremental library updates
Store the voice ID and re-run only new apps when new templates become available:
Voice consistency scoring
Voice consistency scoring
After generating the library, score each piece against the voice rules using Chat with
response_format. Flag any pieces that drift:Parallel generation for speed
Parallel generation for speed
Each generation call is independent — use
asyncio.gather (Python) or Promise.all (JS) to run all 6 apps concurrently instead of sequentially.Credits Estimate
| Operation | Typical Cost | Notes |
|---|---|---|
| Brand voice creation | 50 credits | One-time per voice profile |
| Blog post generation | 15–30 credits | Depends on length (500–1500 words) |
| LinkedIn ad generation | 10–20 credits | Short-form |
| Email sequence (5 emails) | 20–40 credits | Multi-part output |
| Social captions (5 posts) | 10–20 credits | Short-form batch |
| Product description | 10–25 credits | Medium-form |
| Ad copy variants (3) | 10–20 credits | Short-form batch |
| Total (voice + 6 apps) | ~125–205 credits |
What’s Next
Content Repurposing Pipeline
Turn one blog post into 5+ content formats
A/B Copy Production
Same brief, different voices — ready-to-test variants
Brand Voice Extraction & Audit
Score content consistency against extracted voice rules
Content Generation
Full API reference for generation apps
Brand Voice
Create and manage brand voice profiles
Credits & Budget
Usage tracking and cost estimation