Mavera DocsAPI power workflows you can run from Mave
The best API-level operations explained as human prompts: compare, branch, export, track, and automate.
Create an API key safely
Walk through Settings, scopes, one-time key display, and the first API-ready state.
Choose API Keys under For Developers in the sidebar.
Good afternoon
Choose a surface from the sidebar to begin.
- 1Open API KeysChoose API Keys under For Developers in the sidebar.
- 2Name the integrationUse a specific label such as Demo reporting script.
- 3Choose the scopeChoose the minimum simulated workspace scope.
- 4Create the demo keyGenerate a local placeholder. No real credential is created.
- 5Copy it onceCopy the visibly fake demo value and acknowledge that real plaintext is shown once.
You do not need to write code to access most API capabilities. Tell Mave the outcome. The prompts below make the intent explicit enough for her to select the right operation. Developers can automate the same operations through the API.
Compare segments before averaging them
Compare [Audience A] and [Audience B] on [decision]. Where do they agree? Where do they split? Explain the underlying dimension that produces the split and recommend whether we need one message, two messages, or a test to decide.
Make a real file, not just copy
Turn this conversation into a client-ready [Word report / PowerPoint / Excel workbook]. Include our brand voice and colors. Preserve every computed number, label modeled claims, include citations where present, and add an appendix with the method and caveats.
Create an evidence dossier
Gather the files, study output, source quotes, and computed findings in this project into an evidence dossier. Write an executive summary first, then the evidence trail. Make it downloadable and flag any assertion that lacks a source or computed backing.
Export a study for a real analyst
Export the respondent-level and aggregate output from this study. Make a clean CSV plus a one-page methodology note explaining what is synthetic, what is grounded, how shares were computed, and what a human analyst should not infer from it.
Branch instead of rerunning blindly
Branch this insight. Keep the same audience and question, but change [one assumption]. Compare the original and branch side-by-side. Tell me whether the decision changes, not just whether the wording changes.
Track a moving signal
Set up a tracker for [message / competitor / segment signal]. Run it [cadence], use [audience/source], alert when [threshold], spend no more than [credits] per period, and make the digest understandable to a non-researcher.
Ask Mave to teach you
I want to use the advanced capability called [compare audiences / trackers / insight branching / persistent personas / programs]. Explain it in plain English, show me one example from my workspace, estimate the cost, and ask me only the questions you need to run a safe first version.