Two walkthroughs.

Short and concrete. The first pulls a meeting and its summary over the REST API. The second wires your meetings into your editor through MCP and asks a question. Both are copy-pasteable; swap in your own key and meeting id.

01 - Pull a meeting and its summary via the API

You will create a key, list your meetings to get an id, then fetch that meeting and read its summary. About two minutes.

Step 1 - create an API key

Open the API keys page in the app, create a key, and copy it. It is shown once. For convenience, put it in an environment variable so the commands below stay clean:

export NOTABIUM_KEY="ntb_live_..."

Step 2 - list your meetings

Ask for your recent meetings. Each row has an id you will use next.

curl https://api.notabium.com/v1/meetings \
  -H "Authorization: Bearer $NOTABIUM_KEY"

{
  "meetings": [
    {
      "id": "6f1c2e8a-2b4d-4a1e-9c3f-7a0b1d2e3f44",
      "title": "Pricing sync with Acme",
      "status": "complete",
      "duration_s": 1840,
      "created_at": "2026-06-08T15:02:11.000Z"
    }
  ]
}

Step 3 - fetch the meeting

Use the id to pull the full meeting: the row, the transcript, and the outputs.

curl https://api.notabium.com/v1/meetings/6f1c2e8a-2b4d-4a1e-9c3f-7a0b1d2e3f44 \
  -H "Authorization: Bearer $NOTABIUM_KEY"

Step 4 - read the summary

The summary lives in outputs, as the entry whose kind is summary (alongside next_steps and email_draft). With jq you can pull just that:

curl -s https://api.notabium.com/v1/meetings/6f1c2e8a-2b4d-4a1e-9c3f-7a0b1d2e3f44 \
  -H "Authorization: Bearer $NOTABIUM_KEY" \
  | jq -r '.outputs[] | select(.kind=="summary") | .content'

# =>
The team agreed to keep Pro at 19.99/mo and ship a 7-day trial.
Sam owns the pricing-page update; Alex drafts the launch email.

That is it. The same response also carries transcript.full_text and the next_steps and email_draft outputs, so you can push any of it into your own tools. See the REST API reference for the other endpoints.

02 - Query your meetings from your editor via MCP

Here you connect your meetings to an MCP client (Cursor or Claude Desktop) and ask a question in plain language. The assistant does the API calls for you.

Step 1 - create an API key

Same as before: make a key on the API keys page and copy it.

Step 2 - add the Notabium server

In your client's MCP settings, add this server. In Cursor it goes in mcp.json; in Claude Desktop it goes in claude_desktop_config.json under mcpServers. Put your real key in the Authorization header.

{
  "mcpServers": {
    "notabium": {
      "url": "https://api.notabium.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer ntb_live_..."
      }
    }
  }
}

Save, then restart (Claude Desktop) or let the client connect (Cursor). Notabium and its tools appear in the client. Full per-client steps are in the MCP guide.

Step 3 - ask

In the chat, ask in plain language. For example:

The assistant calls search_meetings to find the relevant calls, then ask_meeting or get_meeting to read and answer, and replies with the decision and which meeting it came from. Try a follow-up:

No code, no copy-paste of transcripts. Your meetings are just there, scoped to your key.