1Password

Files and knowledge

1Password for AI agents. Managed auth, ready-made tools.

List vaults and find, read, create and update items in 1Password on behalf of each of your users.

About 1Password

With the 1Password connector, your agent works with the vaults each user gives it in their own 1Password account. It can list vaults, list and read items, create an item and update one, using only the tools your project allows.

1Password is a password manager for storing and sharing passwords, keys and other secrets.

Tools

What your agent can do in 1Password.

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 1Password connection.

  • List vaults

    Read
    onepassword_list_vaults

    List the vaults the connection can access.

  • List items

    Read
    onepassword_list_items

    List the items in a vault.

  • Get an item

    Read
    onepassword_get_item

    Read an item and its fields.

  • Create an item

    Write
    onepassword_create_item

    Create a new item in a vault.

  • Update an item

    Write
    onepassword_update_item

    Change the fields of an item.

Control

Limits you can set.

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

  • Turn single tools on or off

    Let the agent read items, and switch off onepassword_update_item so it can never change a secret.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example one vault but not the others. A call outside them is refused.

Get started

Connect 1Password
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 1Password

    Each end user authorizes their own 1Password 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 1Password account, once.
    const connection = await agent200
      .user("user_123")
      .connect("1password");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the 1Password tools

    Name the user, the model and the tools. The model decides which 1Password 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: "Get the staging database credentials from the DevOps vault",
        tools: ["1password"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own 1Password account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in 1Password, such as listing vaults and reading or writing items in the vaults the user chooses. Users can revoke it later from their 1Password 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 1Password connector and how to use it.

Agent brief
Connector: 1Password, through Agent200. In code: "1password".
What it does: List vaults and find, read, create and update items in 1Password on behalf of each of your users.
Page: https://www.agent200.com/connectors/1password/

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 1Password's own page, through the authorization link Agent200 returns. Never ask a user for a 1Password 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: onepassword_list_vaults, onepassword_list_items, onepassword_get_item. Write tools: onepassword_create_item, onepassword_update_item. Name "1password" 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/1password/framework/claude/
   https://www.agent200.com/connectors/1password/framework/chatgpt/
   https://www.agent200.com/connectors/1password/framework/claude-code/
   https://www.agent200.com/connectors/1password/framework/muse/
   https://www.agent200.com/connectors/1password/framework/grok-bot/
   https://www.agent200.com/connectors/1password/framework/openai-dots/
   https://www.agent200.com/connectors/1password/framework/claude-duet/
   https://www.agent200.com/connectors/1password/framework/hermes-agent/
   https://www.agent200.com/connectors/1password/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/1password.md

Guides

Use 1Password with the AI you build on.

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

FAQ

1Password and Agent200, answered.

Who handles the 1Password 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 1Password.

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 1Password connection, never another user's. It cannot reach anything the user or 1Password has not authorized.

Can I limit what my agent can do in 1Password?

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

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with 1Password.
Your agent does the rest.

Your users connect their own 1Password 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)