Quickstart

From nothing to a working search. Two minutes if you already have an account.

1. Get a key

Sign in, open Settings → API keys, and create one. It is shown once — copy it somewhere safe before you close the dialog.

A key belongs to the team it was created in, and only ever acts for that team. If you are in two teams you will have two keys, and neither reaches the other team's collections, projects or alerts. There is more on this in Authentication.

2. Search something

export SPUTNIK_TOKEN="your-key-here"

curl -H "Authorization: Bearer $SPUTNIK_TOKEN" \
  "https://sputnikintelligence.com/api/v1/posts/search?q=%22your+company%22&window=month"

Quote a phrase you mean as a phrase — that is the single biggest difference between clean results and noise on long-form content. Search syntax covers why.

You get back the shape every list endpoint returns:

{
  "items": [
    {
      "slug": "k3mq-8w1p-ttz4",
      "sputnik_url": "https://sputnikintelligence.com/app/posts/k3mq-8w1p-ttz4",
      "title": "The one where we argue about pricing",
      "link": "https://example.com/episodes/214",
      "published_at": "2026-08-19T06:00:00Z",
      "snippet": "...what <b>your company</b> is doing with...",
      "source": { "slug": "p2ab-99xz-c1dd", "name": "The Example Show" }
    }
  ],
  "total": 37,
  "next_cursor": "50"
}

3. Read the whole thing

A search result is a pointer. To read the episode itself, take the post's slug and ask for its transcript as speaker turns:

curl -H "Authorization: Bearer $SPUTNIK_TOKEN" \
  "https://sputnikintelligence.com/api/v1/posts/k3mq-8w1p-ttz4/transcript"

Names are substituted for "Speaker 1" wherever we could identify who was talking. See Transcripts.

4. Point your agent at it

Everything above is one tool call away for an agent. Connect the MCP server instead of writing HTTP by hand:

https://sputnikintelligence.com/mcp

MCP server has the setup for Claude and for other clients.