Skip to main content

Overview

Buckle connects AI agents to Circleback with an API key. Agents can search your meetings, read notes and transcripts, and manage action items. The gateway injects the key into every request, so your agent never sees it. Connecting takes about a minute.

What you will set up

  • A Circleback API key with read or read and write scope
  • Automatic key injection on every Circleback request
  • Per-agent, per-tool access, with approval for sharing and deleting meetings

Connect Circleback

1

Create an API key in Circleback

In Circleback, open Settings > API keys and click Create API key. Name it Buckle, choose a Scope, and click Create API key.
  • Read lets agents search and read meetings, notes, and action items.
  • Choose a scope with read and write access if agents should also update meetings, action items, or tags.
Circleback API keys settings page with the New API key dialog open, showing a Name field, a Scope dropdown set to Read, and the Create API key button.

Creating an API key in Circleback under Settings > API keys.

Copy the key right away, Circleback only shows it once. Keys start with cb_.
2

Paste it in Buckle

In the Buckle dashboard, open Settings > Apps > Circleback, paste the key into API key, and click Connect Circleback.
Buckle connect window for Circleback, showing a setup guide link, the API key field with a hint to go to Settings, API keys in Circleback, and the Connect Circleback button.

The Circleback connect window in Buckle.

Buckle checks the key with Circleback and names the connection after your Circleback email. A wrong key is rejected right away.
The key has the same access as your Circleback account, so agents reach the meetings you can reach, and no more. Treat it like a password.

What agents can do

Controlling access

Grant the connection to each agent that needs it, and choose per tool what runs freely, what needs approval, and what’s blocked. Meeting notes are sensitive, so a good default is to let agents read freely and put Share meeting and Delete meeting behind approval. Organization rules add guardrails on top. A blocked request never reaches Circleback. To disconnect, remove the connection in Settings > Apps > Circleback, then delete the key in Circleback under Settings > API keys.

FAQ

Create a new key in Circleback under Settings > API keys, then paste it into Settings > Apps > Circleback. Agents pick up the new key automatically. Then delete the old key.
Store it in Buckle. The gateway injects it at the proxy, so the agent never holds the cb_ key. See How it works.
Yes. Create the key with Read scope, or allow only read tools when you grant the connection.