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 just published a 1,200-word blog post about your product launch. Now marketing needs a LinkedIn ad, a Twitter thread, an email drip sequence, a product page summary, and social captions — all derived from the same core narrative. Writing each from scratch is slow and risks message drift. This playbook generates the long-form piece first, then feeds it as context into every subsequent generation app. Each downstream piece inherits the key messages, statistics, and examples from the original — adapted to the format’s constraints (character limits, visual hooks, CTA structure).Mavera-only. No social scheduling platform, no CMS integration. This pipeline produces the content — you publish it wherever you want.
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_...). |
| Brand voice ID (optional) | For consistent voice across all pieces. Create via Brand Voice. |
| Topic and key points | The subject matter for the source blog post. |
| Credits | ~150–350 total. See Credits Estimate. |
| Python 3.8+ or Node.js 18+ | requests + openai SDK for Python; native fetch for Node. |
The Flow
Generate the source blog post
Use
POST /generations with the blog_post_generator app. This produces the canonical long-form content that all downstream pieces will reference.Define the repurposing plan
List the formats you need: LinkedIn ad, Twitter thread, email sequence, product page, social captions. Each maps to a generation app with format-specific input.
Generate each downstream piece
For each format, call
POST /generations with the source blog post injected as additional_context. The generation app adapts the content to the format’s constraints.Generate an executive summary
Use Chat to produce a 150-word executive summary from the blog post — useful for internal stakeholders, newsletters, or Slack announcements.
Stage 1 — Generate the Source Blog Post
Stage 2 — Define the Repurposing Plan
Each downstream piece receives the source blog as context. The generation app handles format adaptation — you provide format-specific instructions.Stage 3 — Generate All Downstream Pieces
Stage 4 — Executive Summary via Chat
Use Chat to generate a concise executive summary from the source blog. Useful for internal Slack posts, newsletter previews, or stakeholder updates.Variations
Start from existing content
Start from existing content
Skip Stage 1 if you already have a published blog post. Load it from a file or your CMS API and use it directly as
source_content for the repurposing loop.Add more formats
Add more formats
Check
GET /generation-apps for new templates (press releases, video scripts, podcast outlines) and append them to REPURPOSE_PLAN.Persona-adapted repurposing
Persona-adapted repurposing
Map each downstream format to a different persona — LinkedIn ads for B2B decision makers, social captions for Gen Z consumers — so each piece speaks to its platform’s primary audience.
Quality gate before downstream generation
Quality gate before downstream generation
Score the source blog post with Chat +
response_format before repurposing. If clarity, accuracy, or engagement scores fall below a threshold, iterate on the source first — repurposing weak content just multiplies the weakness.Parallel generation for speed
Parallel generation for speed
All downstream pieces are independent — use
asyncio.gather (Python) or Promise.all (JS) to run all 5 repurposing calls concurrently instead of sequentially.Consistency check across all pieces
Consistency check across all pieces
After generating everything, feed all outputs into a single Chat call asking it to verify that key metrics (70% reduction, 14→4 days, NPS 32→58) appear consistently. Flag any contradictions or omissions.
Credits Estimate
| Operation | Typical Cost | Notes |
|---|---|---|
| Source blog post | 15–30 credits | Long-form generation |
| LinkedIn ad | 10–20 credits | Short-form |
| Twitter thread (7 tweets) | 10–20 credits | Short-form batch |
| Email nurture (3 emails) | 15–30 credits | Multi-part |
| Product description | 10–25 credits | Medium-form |
| Social captions (5 posts) | 10–20 credits | Short-form batch |
| Executive summary (Chat) | 1–5 credits | Single chat call |
| Total (7 pieces) | ~70–150 credits | Without brand voice creation |
| Total (with new brand voice) | ~120–200 credits | One-time voice + all pieces |
What’s Next
Brand Voice Content Library
Create a full content library with consistent brand voice
Content Series Generation
Turn the source blog into a multi-part series before repurposing
A/B Copy Production
Generate A/B variants of each repurposed piece
Content Localization
Localize the repurposed content for different markets
Content Generation
Full API reference for generation apps
Credits & Budget
Track and manage credit usage