spinach.ai

Developer tools

spinach.ai for AI agents. Managed auth, ready-made tools.

Find past meetings and read their summaries, action items and transcripts in spinach.ai on behalf of each of your users.

About spinach.ai

With the spinach.ai connector, your agent works with each user’s own spinach.ai meeting notes. It can list past meetings and read a meeting’s summary, action items and transcript, using only the tools your project allows.

spinach.ai is an AI meeting assistant that takes notes and action items in video calls.

Tools

What your agent can do in spinach.ai.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own spinach.ai connection.

  • List meetings

    Read
    spinach_ai_list_meetings

    List the user's recorded meetings.

  • Get a summary

    Read
    spinach_ai_get_summary

    Read the summary of a meeting.

  • Get action items

    Read
    spinach_ai_get_action_items

    Read the action items from a meeting.

  • Get a transcript

    Read
    spinach_ai_get_transcript

    Read the transcript of a meeting.

Control

Limits you can set.

You decide what your agent may do in spinach.ai, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read summaries and action items, and switch off spinach_ai_get_transcript so it never reads full transcripts.

  • Restrict what the agent reaches

    Choose the endpoints a project may use, for example summaries but not transcripts. A call outside them is refused.

Get started

Connect spinach.ai
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect spinach.ai

    Each end user authorizes their own spinach.ai account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own spinach.ai account, once.
    const connection = await agent200
      .user("user_123")
      .connect("spinach_ai");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the spinach.ai tools

    Name the user, the model and the tools. The model decides which spinach.ai tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "What were the action items from this morning's standup",
        tools: ["spinach_ai"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, connecting their own spinach.ai account. Each connection belongs to that user.

  • What access is requested

    Access to the meeting notes the connection needs, such as summaries, action items and transcripts. Users can revoke it later from their spinach.ai account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the spinach.ai connector and how to use it.

Agent brief
Connector: spinach.ai, through Agent200. In code: "spinach_ai".
What it does: Find past meetings and read their summaries, action items and transcripts in spinach.ai on behalf of each of your users.
Page: https://www.agent200.com/connectors/spinach-ai/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on spinach.ai's own page, through the authorization link Agent200 returns. Never ask a user for a spinach.ai password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: spinach_ai_list_meetings, spinach_ai_get_summary, spinach_ai_get_action_items, spinach_ai_get_transcript. Name "spinach_ai" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/spinach-ai/framework/claude/
   https://www.agent200.com/connectors/spinach-ai/framework/chatgpt/
   https://www.agent200.com/connectors/spinach-ai/framework/claude-code/
   https://www.agent200.com/connectors/spinach-ai/framework/muse/
   https://www.agent200.com/connectors/spinach-ai/framework/grok-bot/
   https://www.agent200.com/connectors/spinach-ai/framework/openai-dots/
   https://www.agent200.com/connectors/spinach-ai/framework/claude-duet/
   https://www.agent200.com/connectors/spinach-ai/framework/hermes-agent/
   https://www.agent200.com/connectors/spinach-ai/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/spinach-ai.md

Guides

Use spinach.ai with the AI you build on.

Step-by-step setup for spinach.ai with a specific model, assistant or agent framework.

FAQ

spinach.ai and Agent200, answered.

Who handles the spinach.ai OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for spinach.ai.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's spinach.ai connection, never another user's. It cannot reach anything the user or spinach.ai has not authorized.

Can I limit what my agent can do in spinach.ai?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • GitHub

    GitHub

    Read repositories and work with issues and pull requests as the connected user.

    Managed OAuth Developer tools
  • GitLab

    GitLab

    Review merge requests, file issues, read code and check pipelines in your users' GitLab projects.

    Managed OAuth Developer tools
  • Bitbucket

    Bitbucket

    List and open pull requests, comment, read code and check pipelines in your users' Bitbucket workspaces.

    Managed OAuth Developer tools
  • Jira

    Jira

    Search, create and transition Jira issues for the connected user.

    Managed OAuth Developer tools
200 OK

Start with spinach.ai.
Your agent does the rest.

Your users connect their own spinach.ai accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)