Memo AI Developer API
Connect your meeting transcriptions to AI assistants and your own tools — over an official MCP server and a simple REST API.
Your meetings, via API
Create a key and pull transcripts, summaries and speakers straight from your meetings — over REST or MCP.
curl https://app.memoai.tech/api/v1/developer/transcriptions \
-H "Authorization: Bearer mk_live_your_key_here"Memo AI turns your meetings, calls and recordings into structured knowledge. The Developer API opens programmatic access to it — so you don't just store transcripts, you put them to work.
Ask questions about your meetings in plain language and get answers with links to the exact moment, find decisions and details across hundreds of conversations, run meetings against checklists, collect feedback on a talk, build analytics — or pull all of it into an AI assistant, sync it to your own app, and export the whole archive in one command.
There are two ways in, and most people use both:
What you can build
Ask your AI about any meeting
What did we decide about pricing last week?
Your assistant searches the transcripts and answers with links to the exact moment — no need to replay the recording.
Run meetings against checklists
Did the reps cover every onboarding step on these calls?
Score meetings against your own checklist and get a summary: what was covered, what was missed, where the script slipped.
Get feedback on a talk
Review my pitch: structure, clarity, filler words, what to improve.
Analyse a talk or presentation against your criteria — from the full, timestamped transcript.
Find anything in your archive
Which calls had customers complaining about onboarding?
Search decisions, commitments and details across hundreds of conversations at once — no manual scrubbing.
Export to notes and knowledge bases
Pull meetings as Markdown with YAML frontmatter, ready to drop into Obsidian or a static site. Up to 100 transcriptions as a single ZIP per request.
Sync to your own product
Mirror new transcriptions into your CRM, data warehouse or internal tools — over a simple REST API with a single bearer token.
MCP or REST — which one?
| MCP server | REST API | |
|---|---|---|
| Best for | AI assistants & agents | Your own code / integrations |
| Setup | Paste a config, done | Write HTTP requests |
| Who calls it | Claude, ChatGPT, Cursor, Codex | Your backend, scripts, automations |
| Auth | Same API key | Same API key |
| Start here | MCP Quickstart | REST Quickstart |
They share one key
An API key works for both. Create it once in Settings → API & MCP, then use it for the MCP server, REST calls, or both at the same time.